Support More Adapters

[ranger-ross]

This is a tracking is to track support for various storage adapters.

Planned

• Local File System :heavy_check_mark:
• In Memory :heavy_check_mark:
  • For demoing/testing YakMan (not real world use)
• AWS S3 :heavy_check_mark:
• Azure Storage
• Google Cloud Storage :heavy_check_mark:
  • https://github.com/ranger-ross/yakman/pull/218
• Redis :heavy_check_mark:
  • https://github.com/ranger-ross/yakman/pull/219

Needs research

• DigitalOcean Spaces
• IBM Cloud Object Storage

Backburner

• Postgres SQL
• MySQL
• Other SQL DBs

[ranger-ross]

I after thinking about it, I think maybe we put SQL adapters on the back burner. I think for teams blob storage is going to be more cost efficient and easier to manage.

From a development perspective, I think that schema migrations might be tricky. We are could a Rust SQL migration library but ideally, the application should not have DDL privilege.
If the DB is the same DB that contains important data, you probably dont want your config manager to have that kind of access. At that point, you could run the migrations manually (not great), or create a new database, at which point, you might as well use another adapter because its probably cheaper and easier to setup/maintain.

[ranger-ross]

Rust Azure crate is available but looks like its still getting lots of breaking changes.

I am thinking of focusing on other features while that crate matures. Once YakMan and the Azure crate are closer to being feature complete, we can add Azure support