feature: provider based packaging

[YvanDaSilva]

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.

[dearchap]

@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

[YvanDaSilva]

@dearchap Thanks for your answer.
We could stil put them in a package then that would provide json and yaml.
Alsp I wonder then if TOML could be a candidate to move to a different package.

[abitrolly]

I thought that Go allows to maintain multiple packages in a single repo.

[YvanDaSilva]

I thought that Go allows to maintain multiple packages in a single repo.

It absolutely does.
Having a separate repo is a choice.

You can take a look at koanf repo how you can manage multiple go packages with a single repo.