-
Notifications
You must be signed in to change notification settings - Fork 216
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
Unresolved tag: !Ref in CloudFormation Template #669
Comments
@mcflynt |
Closing. Please let us know if there is anything else we can do. |
in your vscode {
"yaml.customTags": [
"!Sub scalar"
]
} |
Here's the full list based on the AWS CloudFormation intrinsic function docs {
"yaml.customTags": [
"!Base64 scalar",
"!Cidr scalar",
"!And sequence",
"!Equals sequence",
"!If sequence",
"!Not sequence",
"!Or sequence",
"!Condition scalar",
"!FindInMap sequence",
"!GetAtt scalar",
"!GetAtt sequence",
"!GetAZs scalar",
"!ImportValue scalar",
"!Join sequence",
"!Select sequence",
"!Split sequence",
"!Sub scalar",
"!Transform mapping",
"!Ref scalar",
]
} 1 Jun 22: Edited to fix |
Thanks for this list! I am not familiar with yaml, it seems |
Update YAML customTags per this issue: redhat-developer/vscode-yaml#669
Isn't there a way that those settings are part of the extension? |
I have this problem how to fix it Please |
##Description
When the extension is running and I am creating a CloudFormation template, the valid syntax of !Ref EnvironmentName, for example, where EnvironmentName is a Parameter in the template is not recognized. The extension produces a 'Problem' of 'Unresolved tag: !Ref'
Expected Behavior
No syntax errors should be reported as this is a valid syntax
Current Behavior
Steps to Reproduce
Tags:
Environment
Note
The same thing happens with the also valid inline !Sub
Example: BucketName: !Sub 'my-first-bucket-${EnvironmentName}' is highlighted and the Problems report shows Unresolved tag !Sub
The text was updated successfully, but these errors were encountered: