-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Fix cloudformation lint job #10256
Fix cloudformation lint job #10256
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kops-verify-cloudformation |
The dockerfile we were using in the cfn-python-lint repo wasn't actually pinned to the version associated with the git tag, it always installs the latest version. A recent release consolidated error rules regarding invalid values. We use an invalid "us-test-1" region and zones in much of our testing. We used to be able to ignore this "invalid AZ" error, but now we would need to ignore all invalid values for all resource properties. This pins cfn-python-lint to an older version but we'll have to figure out how we want to handle this longer term.
0f9ce1a
to
df1e301
Compare
/lgtm |
The Dockerfile we were using in the cfn-python-lint repo wasn't actually pinned to the version associated with the git tag, it always installs the latest version.
A recent release consolidated error rules regarding invalid values (aws-cloudformation/cfn-lint#1750)
We use an intentionally invalid "us-test-1" region and zones in much of our testing. We used to be able to ignore this "invalid AZ" error (E2510), but now we would need to ignore all invalid values for all resource properties.
This pins cfn-python-lint to an older version by providing our own Dockerfile, but we'll have to figure out how we want to handle this longer term.
Fixes https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kops/9666/pull-kops-verify-cloudformation/1328738395379208192