feat(CodeArtifact): add option to provide aws credentials directly #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TLDR: This PR adds the option to declare AWS credentials directly instead of pulling them from a profile.
Background: We have a project where we need two sets of AWS credentials for our e2e tests (one is for us and one is for our customer). Locally we have two profiles for them, but in our gitlab CI we inject these via environment variables. When I tried to add this plugin to our project I encountered the problem that it only accepts profiles for selecting the correct credentials. This works fine locally but in our CI the plugin simply takes the default credentials from the environment variables which are the wrong ones. As our CI has no profiles we cannot select the correct credentials with this plugin. My solution is to add the option to directly declare the
accessKeyId
andsecretAccessKey
in the configuration (e.g. via environment variables).