Closed ewbankkit closed 6 months ago
We should consider raising this with AWS.
This issue has been open for some time now. Any news on this? Can the community do anything to help here? Is there maybe a PFR at AWS we can push? If AWS won't or cannot fix this due to backwards compatibility maybe its time to think of alternative solutions?
There are a handful of resource types
awscc_groundstation_config
awscc_opensearchservice_domain
awscc_opsworkscm_server
awscc_redshift_cluster
awscc_s3outposts_endpoint
awscc_synthetics_canary
that declare their own top-level
Id
property in the CloudFormation schema, but it is not a primary identifier. This conflicts with the assumptions we make for the synthesizedid
attribute.For now, suppress resource generation for these resource types.
Relates:
156
121