Support AWS AppConfig as remote config store

[eladlachmi]

Preflight Checklist

• [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

Viper doesn't currently support AWS AppConfig for remote configuration.

Proposed Solution

Add support for AWS AppConfig alongside etcd and Consul. We already have a working implementation of an AppConfig client based around the AWS SDK, which I'd happily adapt for use with Viper and contribute.

Alternatives Considered

We have worked with deploy-time solutions (i.e., write AppConfig configuration to a file during deployment and use with Viper). This works for static configuration but doesn't provide the watch functionality (obviously)

Additional Information

No response

[github-actions[bot]]

👋 Thanks for reporting!

A maintainer will take a look at your issue shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news, either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

[octomad]

Biggest thing here would be to refactor it to make it extensible to work with any kind of config provider.