Replies: 1 comment 2 replies
-
Hey,
It’s not something we had in mind but we should be able to figure out the workaround. We can add support for accessing the list of configuration parameters to loaders. Then, the corresponding loader will have to iterate and try to load every key. Doesn’t sound pretty good though. Can we somehow specify keys to load? One solutions that comes into my mind is as follows:
This way, config classes stay unaware of any providers. Related Vault issue: |
Beta Was this translation helpful? Give feedback.
-
Hey! I was looking into integrating with a vault provider like AWS Secrets Manager or Hashicorp Vault. Those services usually require that you provide the names of the individual secrets you want to load. There's usually no endpoint to load all secrets at once. Is this concept fundamentally opposed to how AnywayConfig work? If thats not the case, how would one provide the loader with the secrets that are required to be fetched?
Beta Was this translation helpful? Give feedback.
All reactions