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

Construct scope relocation #201

Closed
1 of 7 tasks
eladb opened this issue Jul 16, 2020 · 1 comment
Closed
1 of 7 tasks

Construct scope relocation #201

eladb opened this issue Jul 16, 2020 · 1 comment
Labels
management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@eladb
Copy link
Contributor

eladb commented Jul 16, 2020

PR Champion
# @RomainMuller

Description

To allow preserving paths and generated identities when refactoring construct trees, we propose to introduce construct.node.relocate(path) which will allow specifying the root path for a scope and all its children.

For example, if I have a set of stacks in production which I want to bundle into a new Stage type so that I can deploy them through CDK Pipelines and deploy them without replacement of resources, I would use relocate() to ensure that all paths and unique IDs are preserved as I refactor my code.

Progress

  • Tracking Issue Created
  • RFC PR Created
  • Core Team Member Assigned
  • Initial Approval / Final Comment Period
  • Ready For Implementation
    • implementation issue 1
  • Resolved
@mrgrain
Copy link
Contributor

mrgrain commented Oct 27, 2023

Marking this RFCs as stale since there has been little recent activity and it is not currently close to getting accepted as-is. We appreciate the effort that has gone into this proposal. Marking an RFCs as stale is not a one-way door. If you have made substantial changes to the proposal, please open a new issue/RFC. You might also consider raising a PR to aws/aws-cdk directly or self-publishing to Construct Hub.

@mrgrain mrgrain closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2023
@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 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

2 participants