Skip to content
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

[Feat]: Re-enable cfn-lint #629

Closed
1 task done
javydekoning opened this issue May 15, 2023 · 2 comments · Fixed by #632
Closed
1 task done

[Feat]: Re-enable cfn-lint #629

javydekoning opened this issue May 15, 2023 · 2 comments · Fixed by #632
Assignees

Comments

@javydekoning
Copy link
Contributor

Describe the feature

Re-enable cfn-lint in megalinter config when megalinter has release a new build with the latest cfn-lint.

Use Case

Re-enable cfn-lint in megalinter config when megalinter has release a new build with the latest cfn-lint.

Proposed Solution

No response

Acknowledgements

  • I may be able to implement this feature request
@nvuillam
Copy link

nvuillam commented May 15, 2023

Will happen with v7 that will be released in the following weeks :)

If you are in a hurry, you can already use beta version, that embeds cfn-lint v0.77.5 :) (compared to 0.76.1 in latest MegaLinter 6.22.2)

Another workaround with current version could be to upgrade cfn-lint in a pre-command before it is called

PRE_COMMANDS:
  - command: pip3 install --no-cache-dir cfn-lint=='0.77.5'
    venv: cfn-lint

@javydekoning
Copy link
Contributor Author

Thanks @nvuillam , appreciate your response here. We'll move to v7 when it's out :-)! For now we are OK as cfn-lint runs in another flow as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants