-
Notifications
You must be signed in to change notification settings - Fork 544
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
Idea: move mimir go client into own package #10315
Comments
I'm not against the proposal, but what's the problem directly importing |
I am not a fan of moving the client outside this repository and introducing another package with APIs and the obligations that come with that. Something like this was proposed before here #6677. There shouldn't be anything preventing the client from being imported as-is like Marco mentioned besides the number of dependencies that Mimir pulls in. |
I think moving it out off this repo would be a bad idea too. These are the benefits I see:
|
Yes Tested it again to load it into my path and it loaded the entire mimir codebase.
|
What is the problem you are trying to solve?
help opensource community use mimir's api to build IaC tools
Which solution do you envision (roughly)?
Extract everything that is in: https://github.com/grafana/mimir/tree/main/pkg/mimirtool/client into its on go package.
Have you considered any alternatives?
writing everything by myself
Any additional context to share?
I think it's interesting that you have this code in multiple repositories yourself.
You can find it in Grizzly, Mimir Tools, and Alloy.
How long do you think this would take to be developed?
Small (<= 1 month dev)
What are the documentation dependencies?
No response
Proposer?
No response
The text was updated successfully, but these errors were encountered: