I was tasked with looking into Secrets Management for our APIs and realized that it would be secure and beneficial if Rewst allowed for connecting with a secrets server (1Pass Connect for example) and using the vault items to access the credentials and only have them at runtime. How this could look: User configures vault as its own integration (since a good amount use REST). (Maybe have a box that denotes it as a vault integration?) The vault integration then is leveraged when setting up other integrations (example: Datto, Ninja, Huntress, etc) by allowing the user to select to use the vault -> use dynamic options generator to list IDs and Names of items (no values of credentials) -> when this configured integration is then called, it reaches out to the secrets server to prevent auth from being reviewed in logs and prevent leakage. This would also help with rotating credentials in line with current best industry standards and prevent stale API keys, stolen credentials, etc as well as minimize impact on labor time when needing to rotate keys for whatever reason.