I've been unsuccessful to decouple the artifact configuration from the workflow definition. this configuration might depend on a local, staging or production environment).įor input artifacts however, you need to specify the endpoint, bucket and key in the artifact definition (in the case of s3). This enables you to decouple the artifact repository configuration from the workflow definition (e.g. The wf controller will upload the output artifacts to the default artifact repository (if available). Not great I agree, but that is how it is today.įor output artifacts, it is sufficient to only specify the name and the path in the wf spec. I think you must specify the key within the bucket, as well as bucket, endpoint etc. I agree, however if the workflow definition defines the artifact type and the key (in case of s3), then the workflow controller should be able to figure out that it could try fetching the artifact from the default artifact repository (if that is s3) or from a referenced artifact location? This resembles more closely like the scenario posted by the OP in this issue #2461 This does not seem to contain any information that can be used to get an artifact. name: hello_world path: /tmp/hello_world.txt
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |