aws-cloudformation / aws-cloudformation/cloudformation-cli-typescript-plugin

Provide stackId in ResourceHandlerRequest

Open
#59 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
46
Forks
18
PR merge metrics
No merged PRs in 30d

Description

It would be really useful to have the `stackId` in the `ResourceHandlerRequest` alongside the `logicalResourceIdentifier`. This also allows us to track where a resource is created so that if someone in a different stack tries to create the same resource we can provide an error saying that a different stack has it, and which one.

The ARN is available on create and update events in the `systemTags`, but not delete events. We need to tidy up our resource ownership registry when a resource is deleted so also need it at that point.

We've worked around its absence by copying chunks of this library into our own project and switching out the BaseResource for our own copy but it would be much easier if it were in the base library.

Contributor guide

Open the contributing guide

Research direction

Start by tracing ResourceHandlerRequest and BaseResource through the plugin, then compare how stack identity is exposed in create, update, and delete events. Check the systemTags path for existing ARN handling. Done means ResourceHandlerRequest provides stackId, including during deletion, without requiring consumers to copy the base library.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, node.js, typescript
Domain
backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.