New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New plugin: AWS CDK Toolkit #232
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would like to leverage the powers of CredentialUsage
field of an Executable
to specify that AWS CDK CLI executable could use the exact same CredentialType
as AWS
does. This will mean that by default, all default provisioners and importers will be re-used for cdk as well.
@AndyTitu I believe that the change that I just pushed conforms with that you're hoping for. Let me know if you think any other changes are necessary! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functionally tested for op plugin run
, op plugin init
, op plugin ls
, op plugin inspect
, and op plugin clear
.
Code lgtm
Summary
Add support for a new plugin for the AWS CDK Toolkit.
The AWS Cloud Development Kit (AWS CDK) lets you define your cloud infrastructure as code in one of its supported programming languages. You can use it to create, manage, deploy, etc. AWS CDK apps.
Thought Process
The AWS CDK Toolkit uses the same credentials as the regular AWS CLI, and the same profile workflow. We can reuse the importers and provisioners that have already been created for the AWS shell plugin.
How To Test
op plugin init cdk
cdk
command from the CDK app directory that requires authentication, e.g.cdk deploy
. Try authenticating in the following ways. The command should be authenticated and run as expected:a. Use an existing
AWS Access Key
created for the regular AWS shell pluginb. Import credentials from the
~/.aws/credentials
filec. Import credentials manually as prompted
make aws/validate
. All validation checks should pass and there should be a# Executable: AWS CDK Toolkit
section