S3Artifact endpoint can be set to be insecure (HTTP); Secrets do not have the "namespace: default" entry when no namespace is specified. This enables the use of S3Artifacts when running workflow in a namespace other than "default".
What changes were proposed in this pull request?
Added a new argument insecure to the create_s3_artifact function.
Secret yaml file does not put the "namespace: default" entry when no namespace is specified.
Why are the changes needed?
S3Artifact Endpoint can be HTTP now
Secret yaml file does not put the "namespace: default" entry when no namespace is specified. This enables the use of S3Artifacts to be used when workflow is submitted to a namespace other than "default". Previously it would cause an error where the secret created by the S3Artifact always has the "namespace: default" entry no matter which namespace the workflow is being submitted to.
How was this patch tested?
Existing unit tests passed. Couple of changes were made to the test methods to test the new source changes.
S3Artifact endpoint can be set to be insecure (HTTP); Secrets do not have the "namespace: default" entry when no namespace is specified. This enables the use of S3Artifacts when running workflow in a namespace other than "default".
What changes were proposed in this pull request?
insecure
to thecreate_s3_artifact
function.Why are the changes needed?
How was this patch tested?
Existing unit tests passed. Couple of changes were made to the test methods to test the new source changes.