Connector Improvement: Additional properties for custom cloud connectors
CompletedI love the recent(?) change that allows creating/editing individual secrets for custom cloud connectors. Is there any way we'd be able to have a section like that for additional properties/arguments? (i.e. "secrets that don't actually need to be secret")
We have a few connectors that accept certain values from the user to determine what data to process or how to process it. These are usually environment names ("Production", "Test", etc.), tenant identifiers, or other IDs, which would be okay to have visible in the configuration page of a connector.
Our current workaround is to just have these values input as a secret (or hard-coded in the function itself), but it would be nice to have an additional section in Fivetran's UI for these optional settings.
-
Official comment
Hi Ernie,
Yes this was added to AWS Lambda just last month. We will be rolling it out to Google Cloud Functions and Azure Functions soon.
Thank you for taking the time to submit the feature request.Best Regards
Alison
-
Looks like this is redundant now since Fivetran provides a "customPayload" object on requests. I'm not sure if this was added recently and/or if I just missed it in the documentation. I'll do some testing shortly to confirm it's the functionality I was looking for.
-
I tested the Custom Payloads feature with one of our Azure Functions and it worked exactly as expected. Great timing!
Please sign in to leave a comment.
Comments
3 comments