aws-cloudformation / aws-cloudformation/cloudformation-cli

Feature request: register-type under a different name

Open
#903 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
336
Forks
172
Avg merge
3d 5m
Merged PRs (30d)
3

Description

Hi!

When I use `aws cloudformation register-type --type-name My::Resource::Test --schema-handler-package ...` then the type-name needs to match the name in the schema handler package. While that is useful to find typos and such, it makes testing harder.

I would like to add to my type-name something like a build number so I can run multiple builds in parallel which deploy my resource and test it without interfering with each other. Maybe we can add another flag --allow-type-name-mismach?

Cheers
Ruwen

Contributor guide

Open the contributing guide

Research direction

Start by locating the CLI entry point for `aws cloudformation register-type` and the validation that compares `--type-name` with the schema handler package. Clarify the intended mismatch behavior and flag spelling, then add tests showing parallel build-specific names work without weakening unrelated validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cli, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.