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

Precise AWS::StackId, AWS::StackName handling #246

Open
t0yv0 opened this issue Nov 22, 2024 · 0 comments
Open

Precise AWS::StackId, AWS::StackName handling #246

t0yv0 opened this issue Nov 22, 2024 · 0 comments
Labels
kind/enhancement Improvements or new features

Comments

@t0yv0
Copy link
Member

t0yv0 commented Nov 22, 2024

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

CloudFormation Ref intrinsic may resolve pseudo-parameters such as AWS::StackId, AWS::NotificationARNs, AWS::StackName.

In pulumi-cdk these are currently replaced by the CDK stack node ID. For most applications there should be no impact as these are used as FYI labels. This issue is tracking eventually getting the pulumi-cdk behavior to line up precisely with CloudFormation to make this correct for applications where it does matter.

Affected area/feature

@t0yv0 t0yv0 added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Nov 22, 2024
@t0yv0 t0yv0 changed the title Precise AWS::StackId, AWS::NotificationARNs, AWS::StackName handling Precise AWS::StackId, AWS::StackName handling Nov 25, 2024
@t0yv0 t0yv0 removed the needs-triage Needs attention from the triage team label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

1 participant