We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
AWS::CloudFormation::Type - can create resource via API, but not via CloudFormation
In Create, it should register the type and set it as the default version
In Update, it should register a new type (using the same name), set it as the default version, and deregister the old version
In Delete, it should deregister the current version
Updates to the resource changing the name should be rejected.
Management
The text was updated successfully, but these errors were encountered:
This was actually already requested, but I moved the issue over here
I have a PR up for schema discussion in that repo, feel free to chime in 👍
I have a basic codebase nearly ready to add there too.
Sorry, something went wrong.
Is this now resolved from this merge? aws-cloudformation/aws-cloudformation-resource-providers-cloudformation#4
It's only resolved once it ships in CloudFormation proper. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_CloudFormation.html
Any word on when this actually going live?
CloudFormation now supports the following resources: AWS::CloudFormation::ResourceDefaultVersion AWS::CloudFormation::ResourceVersion
Thank you!
rjlohan
No branches or pull requests
Scope of request
AWS::CloudFormation::Type - can create resource via API, but not via CloudFormation
Expected behavior
In Create, it should register the type and set it as the default version
In Update, it should register a new type (using the same name), set it as the default version, and deregister the old version
In Delete, it should deregister the current version
Updates to the resource changing the name should be rejected.
Links
Category
Management
The text was updated successfully, but these errors were encountered: