CDK Debootstrap Command
- Dominant language
- JavaScript
- Stars
- 572
- Forks
- 108
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
## Description
Removes the CDK bootstrap stack and all associated resources from an AWS environment that get created when `cdk bootstrap` is run.
## Roles
| Role | User
|---------------------|------------------------------
| Proposed by | @sanjanaravikumar-az
| Author(s) | @sanjanaravikumar-az
| API Bar Raiser | @rix0rrr
| Stakeholders | @alias, @alias, @alias
> See [RFC Process](https://github.com/aws/aws-cdk-rfcs#rfc-process) for details
## Workflow
- [x] Tracking issue created (label: `status/proposed`)
- [x] API bar raiser assigned (ping us at [#aws-cdk-rfcs](https://cdk-dev.slack.com/archives/C025ZFGMUCD) if needed)
- [x] Kick off meeting
- [x] RFC pull request submitted (label: `status/review`)
- [x] Community reach out (via Slack and/or Twitter)
- [ ] API signed-off (label `status/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.
Contributor guide
Research direction
No implementation files, tests, or entry points are named. Start by reading the RFC description and the linked RFC Process, then follow the checklist; completion is represented by the RFC reaching the approved and implementation-complete stages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cli, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100