I'm unclear on the plans for CloudFormation resource types representing registry types. The PR for AWS::CloudFormation::ResourceVersion, #4, was merged in August, but is not yet part of the public CloudFormation resources. The PR for AWS::CloudFormation::ModuleVersion #32 was merged in December and is available. There's now a PR merged for AWS::CloudFormation::TypeVersion #39.
I believe strongly that types in the registry (resource, module, ...) need separate CloudFormation resource types. A module is not the same as a resource provider. I appreciate that AWS::CloudFormation::TypeVersion will provide a backstop when new registry types are rolled out, so that people can use them immediately, but this should not preempt the creation of dedicated resource types for new registry types.
When is AWS::CloudFormation::ResourceVersion going to come out? Can you confirm that the plan is to have resource types corresponding to registry types, and not to just dump ::TypeVersion on customers and leave it at that?
I'm unclear on the plans for CloudFormation resource types representing registry types. The PR for
AWS::CloudFormation::ResourceVersion, #4, was merged in August, but is not yet part of the public CloudFormation resources. The PR forAWS::CloudFormation::ModuleVersion#32 was merged in December and is available. There's now a PR merged forAWS::CloudFormation::TypeVersion#39.I believe strongly that types in the registry (resource, module, ...) need separate CloudFormation resource types. A module is not the same as a resource provider. I appreciate that
AWS::CloudFormation::TypeVersionwill provide a backstop when new registry types are rolled out, so that people can use them immediately, but this should not preempt the creation of dedicated resource types for new registry types.When is
AWS::CloudFormation::ResourceVersiongoing to come out? Can you confirm that the plan is to have resource types corresponding to registry types, and not to just dump::TypeVersionon customers and leave it at that?