Draft: Move crds to sub folder #511
Closed
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
|
Hi @eyarz Would you comment on this PR before I put more work into it to bring it up-to-date? BR |
|
I think you will make a lot of people mad because you will break their pipeline that is directed to look for the CRDs at |
I see. |
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.
This builds on top of PR #510. If #510 is approved / merged, I will rebase this PR. But I add it here now to start a conversation :)
I suggest moving the CRDs into a subfolder
crds. Motivation: Separate content (CRDs) from supporting elements, and thus keeping a better overview.@eyarz: Does this interfere with something in your setup / something on your side?