Pipeline fails on importing external resources
Summary
The pipeline is failing on the import artifacts script due to a possible issue with the way the hardening-manifest.yaml is setup.
Link to failed pipeline
Job #1177435 failed for ae2c0549
What is the current bug behavior?
Pipeline fails due to being unable to access the S3 access/key environment variables due to a possible improper reading of the hardening-manifest.yaml (which may or may not be being auto-generated).
What is the expected correct behavior?
The pipeline pulls the required credential_id from the hardening-manifest.yaml and is able to access the s3 environment variable/credentials for pulling external resources.
Possible fixes
I believe the pipeline job is failing due to some error in the hardening manifest generation. I debugged this failure by running a subsection of the downloader.py script file against the download.json that I am attempting to provide and it properly identifies the local S3 environment variables that are set on my dev environment.
Definition of Done
-
Pipeline failure has been resolved
