OLH-1904 Fix CFN-lint errors on template.yaml #250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aenciso
force-pushed
the
OLH-1904-Fix-CFN-Lint-issue-on-Backend-Repo
branch
from
ae01178
to
0733cef
Compare
alex9smith
approved these changes
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
OLH-1904
What changed
tamplate.yaml has been updated to fix the errors reported by cfn-lint@1.3.3
Why did it change
So that publishing to backend repo to dev can work successfully
Related links
Checklists
Environment variables or secrets
Permissions
Testing
Ran cfn-lint locally to ensure no errors are reported
How to review
Run cfn-lint locally