-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
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
Rename reference to **AWS CloudFormation** in the resource schema #1784
base: main
Are you sure you want to change the base?
Conversation
Example output
|
Hi @wellsiau-aws 👋 , Something like this was my first thought as well, however I don’t think it will do the right thing on all occasions. So if we do move forward with this approach we would need to be comfortable with those tradeoffs. The usage of CloudFormation in the documentation occurs in a number of different contexts in which replacing it with Terraform can be correct, incorrect or even confusing. There are also a few permutations of CloudFormation to consider, Below are a non-exhaustive set of examples of what effects this approach might have where the output is non-ideal, there are about 109 mentions of CloudFormation (excluding CloudFormation Resources) in the documentation: awscc_applicationautoscaling_scalable_target
This would be renamed to “Terraform Template Stack” and be potentially misleading. Generally the “stack” verbiage is problematic, although it may make sense in some occasions. awscc_appsync_function_configuration
I think this is correct in intent, but the term template doesn’t map well with Terraform terminology. awscc_autoscaling_auto_scaling_group
It's fine to link to CloudFormation documentation for more information, however this would rename would suggest a Terraform guide rather than a CloudFormation one. awscc_cloudtrail_resource_policy
I would assume that using YAML would work correctly for this resource policy, however the rename would not be entirely correct. awscc_codestarconnections_sync_configuration
Correct, however we probably don’t want to use the term stacks. awscc_ec2_vpc_endpoint
Not correct to convert. awscc_gamelift_fleet
Mentions of CloudFormation specific functions awscc_grafana_workspace
In this case the attribute is specifically a CloudFormation references and should not be renamed. awscc_kms_alias
Mention of CFN |
@breathingdust , yes, that is the same concern I had as I started to explore this option. if we are committed to explore this path, I think we could modify the The best solution obviously is to have this addressed by the upstream Cfn schema in form of keyword replacement vs literal mention of CloudFormation. |
Community Note
Relates OR Closes #1783
This new function will run after schemas is downloaded and will check for any reference to AWS CloudFormation within the schema.