Skip to content
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

CDK Operator CLI #418

Closed
1 of 11 tasks
Chriscbr opened this issue Apr 8, 2022 · 1 comment
Closed
1 of 11 tasks

CDK Operator CLI #418

Chriscbr opened this issue Apr 8, 2022 · 1 comment
Labels
bar-raiser/needed management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@Chriscbr
Copy link
Contributor

Chriscbr commented Apr 8, 2022

Description

A command line tool that allows CDK builders and operators to run commands associated with L2 and L3 constructs from their terminal. This extends the "abstraction" provided by constructs to the space of command line tools.

For example, when you created a CDK construct named "MyBucket" and deployed it to your account, instead of running:

aws s3api get-object --bucket mybucketf68f3ff0-abcdefg --key file.txt

... you could instead run:

cdk-app MyBucket get-object file.txt

Each construct type would be associated with a list of commands, which could have different parameters etc.

Possible features:

  • simple syntax for specifying command arguments and flags
  • option for commands to invoke bash scripts
  • option for commands to execute SSM runbooks
  • commands that allow you to view AWS CDK resources directly in AWS console (opens your browser)
  • commands for user-made constructs
  • convenient "help" screens
  • command that helps you discover vailable constructs, or that lets you view into the construct tree interactively
  • choose constructs by tag or by metadata instead of by name
  • run commands on multiple constructs?
  • interface / extension points allowing the tool used for other CDKs such as cdk8s and cdktf

Roles

Role User
Proposed by @Chriscbr
Author(s) @alias, @alias, @alias
API Bar Raiser @alias
Stakeholders @alias, @alias, @alias

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
  • Kick off meeting
  • RFC pull request submitted (label: status/review)
  • Community reach out (via Slack and/or Twitter)
  • API signed-off (label api-approved applied to pull request)
  • Final comments period (label: status/final-comments-period)
  • Approved and merged (label: status/approved)
  • Execution plan submitted (label: status/planning)
  • Plan approved and merged (label: status/implementing)
  • Implementation complete (label: status/done)

Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.

@mrgrain mrgrain added status/stale The RFC did not get any significant enough progress or tracking and has become stale. and removed status/proposed Newly proposed RFC labels Oct 13, 2023
@awsmjs
Copy link
Contributor

awsmjs commented Dec 15, 2023

Closing as this ticket has gone stale and is not a current priority.

@awsmjs awsmjs closed this as completed Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bar-raiser/needed management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants