-
Notifications
You must be signed in to change notification settings - Fork 3
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
feature: provider based packaging #10
Comments
@YvanDaSilva that makes sense. In this case json/yaml etc share a lot in common so we had used a common infrastructure for that. if you are doing any providers totally different from them then yeah putting it in a separate dir/package is better |
@dearchap Thanks for your answer. |
I thought that Go allows to maintain multiple packages in a single repo. |
It absolutely does. You can take a look at koanf repo how you can manage multiple go packages with a single repo. |
Hello,
Looking at this repo while trying CLI V3, I noticed that all altsrc are on the same package.
Since you moved these sources to a separate repository, I assume you would want to add more providers.
Because of this I would expect to not have to import all supported config providers if I don't need them.
I.E. vault, aws secrets, one password, etc.
Would you be interested in this change?
Keep up the great work.
The text was updated successfully, but these errors were encountered: