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

Generate Kubernetes style api objects #1789

Open
benmathews opened this issue Dec 13, 2024 · 3 comments
Open

Generate Kubernetes style api objects #1789

benmathews opened this issue Dec 13, 2024 · 3 comments

Comments

@benmathews
Copy link

I would like to interact with the RabbitMQ CRDs via Kubernetes style api objects.

This would require running [kube_codegen.sh] against the type definitions.

@mkuratczyk
Copy link
Collaborator

Can you elaborate on this? What does this enable you to do?
Also, can you submit a PR for the change you would like to see?

@benmathews
Copy link
Author

I would like to interact with the RabbitMQ CRDs as described in this blog post and this associated code repo. It would allow something like

rabbitClient, _ := clientset.NewForConfig(config)
rabbits, err := rabbitClient.RabbitMQ().Rabbits(*namespace).List(context.Background(), metav1.ListOptions{})

Once I have the RabbitMQ configuration, I can generate configuration for my applications that use RabbitMQ. Currently we are hand configuring it. I'd like to automate that burden.

At the time, I don't think my company has the motivation to implement this themselves.

@Zerpet
Copy link
Collaborator

Zerpet commented Dec 20, 2024

We never intended for this Operator to be consumed as a library. In fact, we bump the go and the toolchain directives assuming this is an application, not a library. I know there are some projects out there that consume this project as a Go library, and we try to not break them, or at least not very often.

The proposed change could be beneficial for this operator to make the code more readable, in addition to the automation benefit mentioned.

If anybody wants to contribute this change, it would be most welcome. For our very small team, a cosmetic change like this sits at a low priority.

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

No branches or pull requests

3 participants