enable NoMaps Linter#8098
Conversation
|
@simonpasquier PTAL |
simonpasquier
left a comment
There was a problem hiding this comment.
Thanks for the PR! We can't change the structure of the APIs because it would break users. Instead I recommend to configure exceptions for all existing maps.
ebb8c20 to
35d6993
Compare
@simonpasquier i configured the nomaps lint exception for all the existing maps keeping the APIs structure preserved. |
7cab6ad to
83a36ba
Compare
83a36ba to
46b0bef
Compare
|
@simonpasquier i have fixed the crd validations differences , nomaps kal linter is now configured for all the existing maps exceptionally without any user breakage |
heliapb
left a comment
There was a problem hiding this comment.
Hi @kartikangiras could you pls check there seems to merge conflicts, could you rebase so to tackle those. Thanks
59a68e7 to
e3c2d87
Compare
@heliapb resolved. |
|
ah can you rebase? |
e3c2d87 to
6439b66
Compare
6439b66 to
8bdd368
Compare
|
@simonpasquier done rebased. |
Description
NoMaps KAL Linter enabled for API types
Realted to #7870
Closes #8135
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.