Other: System Keys with all permissions permanently
Not planned
Currently we specify all the permissions when creating a System Key. I cannot currently see a UI mechanism for updating those permissions (although the API appears to exist for it) when a new permission is added.
It would be useful to be able to create a System Key that would always have every permission at a set level, so we can use that for privileged systems, like Terraform.
-
Official comment
Hi Awad,
agreed re: ability to edit System Key permissions on the UI to add permissions manually if needed.
You're right there isn't a way to do that at the moment.
We're considering a new, more comprehensive feature to replace System Keys and I will absolutely add this to the requirements for our evolution of System API Keys. We're going on focus on making functional enhancements to that evolution.
Thank you again for helping us improve Fivetran!
Best regards,
Pieter Humphrey -
Hi Awad,
Thank you for submitting your feature request for "System Keys with all permissions permanently." We appreciate you taking the time to share your ideas with us.
At this time, this feature is not on our current product roadmap. We rely heavily on the feedback and upvotes within this portal to gauge interest and prioritize our development efforts. Every upvote on this request helps strengthen the case to consider it for future releases.
To better understand how this capability would help your organization—and to help us justify future commitment—I’d love to hear more about your specific use case. Could you share details about the scenarios where permanent system keys with all permissions would make the biggest impact for you?
Thanks again for reaching out and helping us shape the future of Fivetran.
Best regards,
Pieter Humphrey -
Hi Awad,
Thank you for submitting your feature request for "System Keys with all permissions permanently." We appreciate you taking the time to share your ideas and help us improve Fivetran.
At this time, this specific feature is not on our current roadmap. However, community feedback and upvotes are key factors we consider when prioritizing new developments. Every upvote on this request strengthens the case for future consideration, so please encourage others with similar needs to support it.
To help us better understand your use case and to justify potential future investment, could you share more details about the scenarios where permanently enabled system keys would make a difference for your team?
Thank you again for engaging with us!
Best,
Pieter Humphrey -
We use Terraform to spin up the largest part of our setup in Fivetran. Quite often that gets run from CD pipelines where it doesn't have user credentials to work with. System Keys are a useful feature to make that happen, but we'd need to be able to update the permissions on a System Key when new features are added to the API (e.g. Transformations) or have a Key that is expected to 'auto-update' to always have all the permissions.
-
Understood re: Terraform - thanks. When we add new features to the API, I'm not sure that auto-updating an existing key would be a secure practice, as it may inadvertently entitle your CI/CD pipleline to something it shouldn't. I can see why it would be convenient and/or be a timesaver, though, but that can often be how system security gets exploited. -
Agreed that the security boundary is requires thinking about and is very dependent on the scope of the deployment in question.
There is a second part to this suggestion though, which is being able to edit System Key permissions on the UI to add permissions manually if needed. I can't spot a way to do that at the moment.
Please sign in to leave a comment.
Comments
6 comments