cdk.go: support --profile flag by adding missing provisioner #463
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.
Overview
Fixes the cdk plugin not handling the
--profile
flag correctly when a profile is using role assumption. Now it matches the expected behavior of the aws plugin's--profile
flag and theAWS_PROFILE
environment variable.Type of change
How To Test
If you have an existing CDK stack, you can confirm that using a profile to assume a role used for deployments.
Example
~/.aws/config
file. Swap out with names and numbers from your accountWithout the patch, the cdk will encounter the error below and fail
Changelog
AWS CDK Plugin now supports AWS Profiles that assume a role, when specified by the
--plugin
flag.