Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add PipelineConfig to api to re-implement pipeline-level config
Browse files Browse the repository at this point in the history
KFP v1 supported setting pipeline-level configuration via a
`PipelineConf` class. This class was deprecated and no replacement
was added to KFP v2.

add new PipelineConfig message in the api to support setting
pipeline-level configuration in KFP v2.

Signed-off-by: Greg Sheremeta <gshereme@redhat.com>
gregsheremeta committed Oct 28, 2024
1 parent c5f162d commit 009132a
Showing 2 changed files with 1,524 additions and 1,293 deletions.
2,809 changes: 1,517 additions & 1,292 deletions api/v2alpha1/go/pipelinespec/pipeline_spec.pb.go

Large diffs are not rendered by default.

8 changes: 7 additions & 1 deletion api/v2alpha1/pipeline_spec.proto
Original file line number Diff line number Diff line change
@@ -1091,11 +1091,17 @@ message SinglePlatformSpec {
// Arbitrary configuration, which will be defined by the platform
// protos/libraries.
google.protobuf.Struct config = 3;
}

PipelineConfig pipelineConfig = 4;
}

message PlatformDeploymentConfig {
// Map of executor label to executor-level config
// Mirrors PipelineSpec.deployment_spec.executors structure
map<string, google.protobuf.Struct> executors = 1;
}

// Spec for pipeline-level config options. See PipelineConfig DSL class.
message PipelineConfig {
// TODO add pipeline-level configs
}

0 comments on commit 009132a

Please sign in to comment.