I have removed the API key string and replaced it with a required env var, "$SDKMS_API_KEY" by default.
The rest of the pipeline was uncommented and filled out so, if done correctly, should now run your "gettest" job before producing a new production version.
You will not need to manually create a production version. Assuming everything is working, once the branch is merged into master you should see the "integration-tests_prod-release" workflow run with the "integration-master_filters" filters, triggering the production deploy
Two notes:
Examples: Rename example.yml to the name of the example you would like to show and demonstrate how to utilize one of the commands in the orb. Consider adding examples for both jobs and perhaps the store-secret and get-secret commands.
The orb will need to be re-tested after these changes. within Get-secrets I noticed a ">>" which was showing as an error in my linter. I believe this may interfere with the "<<>>" from parameters but was having some trouble finding that documentation. If this worked previously with no issue then we could remove this. Otherwise I believe this should resolve the issue.
Hello,
I have removed the API key string and replaced it with a required env var, "$SDKMS_API_KEY" by default.
The rest of the pipeline was uncommented and filled out so, if done correctly, should now run your "gettest" job before producing a new production version.
You will not need to manually create a production version. Assuming everything is working, once the branch is merged into master you should see the "integration-tests_prod-release" workflow run with the "integration-master_filters" filters, triggering the production deploy
Two notes:
Examples: Rename example.yml to the name of the example you would like to show and demonstrate how to utilize one of the commands in the orb. Consider adding examples for both jobs and perhaps the store-secret and get-secret commands.
The orb will need to be re-tested after these changes. within Get-secrets I noticed a ">>" which was showing as an error in my linter. I believe this may interfere with the "<<>>" from parameters but was having some trouble finding that documentation. If this worked previously with no issue then we could remove this. Otherwise I believe this should resolve the issue.