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

Rename the CRD files. #1210

Merged
merged 4 commits into from
Dec 20, 2019
Merged

Rename the CRD files. #1210

merged 4 commits into from
Dec 20, 2019

Conversation

porridge
Copy link
Member

@porridge porridge commented Dec 19, 2019

What this PR does / why we need it:

This is in preparation for moving to controller-gen, which is somewhat
opinionated in that it does not allow us to pick the exact file names.

I guess we do not really care what these are called anyway - the only
place on all of GitHub where these names show up is this integration test - so pleasing controller-gen now will make future diffs smaller.

This is another baby step towards #862

It was never used (verified by eyeballing `git log -p` all the way
down), we don't seem to know what it's for, and it has no counterpart in
the structs.
This is in preparation for moving to `controller-gen`, which is somewhat
opinionated in that it does not allow us to pick the exact file names.

I guess we do not really care what these are called anyway - the only
place where these names show up is this integration test.
Copy link
Contributor

@alenkacz alenkacz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm the dot in the file name - not a big fan :/ also we lost the version there, how are we going to distinguish multiple versions?

Really no way to customize this? :(

@porridge porridge changed the base branch from crd-correction-crdversion to master December 19, 2019 10:24
@porridge
Copy link
Member Author

Hmm the dot in the file name - not a big fan :/

May I ask why it matters?

also we lost the version there, how are we going to distinguish multiple versions?

Looks like this will be handled automagically If we have more than one.

Really no way to customize this? :(

Looking at that code, it doesn't seem like it...

Copy link
Contributor

@alenkacz alenkacz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@porridge

May I ask why it matters? - just a matter of taste

Looks like this will be handled automagically If we have more than one. - oh that's version of CRD resource, not version of our CRDs, anyway, now I realized that multiple versions are actually represented by one yaml so all good. 👍

@porridge porridge merged commit 8412987 into master Dec 20, 2019
@porridge porridge mentioned this pull request Jan 7, 2020
2 tasks
ANeumann82 pushed a commit that referenced this pull request Feb 13, 2020
This is in preparation for moving to `controller-gen`, which is somewhat
opinionated in that it does not allow us to pick the exact file names.

I guess we do not really care *that much* what these are called anyway - the only
place where these names show up is this integration test.

Signed-off-by: Andreas Neumann <aneumann@mesosphere.com>
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 this pull request may close these issues.

None yet

2 participants