-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Make it possible to configure where the CRD is generated? #2842
Comments
I would go for providing a configuration option with a default value. |
Yes, that was my plan as well. I'm just not sure what's the best way to configure it. |
In relation with #2836 it should be really easy once the CRD-Generator has its own API. For the APT usage, then probably an annotation or a Maven->System property are the ways to go. |
This issue was mostly about the Java Operator SDK work so that CRDs could be generated in the same spot as the files that the Quarkus Kubernetes extension. This was worked around in the Quarkus extension for the Java Operator SDK. While the underlying issue is still valid, there's no more need for this at the moment so closing it for now. |
It would make sense to generate all kubernetes-related artifacts in a single location for a given project. As some other projects also generate kubernetes artifacts (dekorate, quarkus), it would make sense for users to be able to select where the CRDs are generated.
Thoughts, @iocanel @manusa?
The text was updated successfully, but these errors were encountered: