Connector Improvement: AWS Lambda Secret Management
Completed
Situation: we want to pass multiple secrets to a custom connector through Fivetran.
Issue: updating a single secret requires the user to be aware of all other secrets and the structure of secret object passed as JSON, in order to re-create the whole object, although only 1 secret needs updating.
Proposal: allow secrets to be passed as key:value pairs from the interface individually. With visible keys and hidden values, a single secret could be updated without compromising on the confidentiality or requiring knowledge of existing secrets or structure.
-
Official comment
Hi Gerrit,
Thank you for sharing this enhancement request. Would it be possible to describe a little more about when you need to send multiple secrets to a function connector?
How common is it that you find yourself in the position where the same function needs to have many secrets - again if you could share specific instances I would greatly appreciate it.
Regards
Alison
-
Hi Alison, sure. For example when using a connector to get data from an API we need to pass in the API token, but also want to utilize our centralized logging/tracing service, for which we also need a token. Now if there is the need to modify the logging token, we would currently also need to re-enter the API token.
So you can see this use case is very typical for us, since we utilize this logging/tracing service in all custom code we write. -
Hi Gerrit,
That's a great example thank you so much for sharing. I'll get the team looking into our options for adding this to the roadmap.
Alison
-
Hi Gerrit,
An update adding this feature is just about to launch.
Thank you so much for the suggestion
Alison
Please sign in to leave a comment.
Comments
4 comments