Please pin cfn-lint to newer release
See original GitHub issueIn order to install a project where cfn-lint is a dependency, poetry downloads every single possible version of cfn-lint allowed by all the version ranges specified by dependencies in your project. Moto currently has a version restriction of >0.4.0
. For a project like cfn-lint that issues new releases regularly (and at this stage probably has over 100 releases satisfied by that constraint), this results in poetry taking a significantly long time when using a private package registry.
I know this isn’t moto’s fault, but is there any chance you could bump the version constraint so that less versions need to be checked? 0.4.0 is very very old nowadays.
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
CFN Lint: AWS CloudFormation Linter - Morioh
AWS CloudFormation Linter, Validate AWS CloudFormation yaml/json templates against the AWS CloudFormation Resource Specification and additional checks.
Read more >Spinnaker Release 1.18.0
This new feature enables users to pause the pipeline execution until the user executes the change manually through Deck itself without having to...
Read more >2020 Fire Code of New York State
This 2020 Fire Code of New York State is a copyrighted work owned by the International Code. Council, Inc., (“ICC”). This work contains:...
Read more >Is there a way to unit test AWS Cloudformation template
Here's a breakdown of how several methods of testing software can be applied to CloudFormation templates/stacks: Linting.
Read more >No-See-Ums, But You Feel 'Em - Bug Squad - ANR Blogs
For noseeum bites---take a straight pin and insert it in the top layer of skin above the bite, making a couple small holes...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You’d think! But in my experience, any project/business of a certain age will have weird rules/constraints in place that forces developers to pin dependencies.
I’ll pin
cfn-lint
to 0.40.0 instead. That’s does have Python classifiers, is ‘only’ 2 years old, and still gives people a large range of versions to use.Thank you so much ❤️