You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am pushing Fivetran teams from Okta and would like to be able to manage the permissions they have (on an account level), with Terraform.
At the moment I see I can create teams, and manage their account role, like this:
resource "fivetran_team" "admin" {
name = "Admins"
role = "Account Administrator"
}
However, that is forcing me to import the group if Okta has already created it. Otherwise, it tries to create a new one.
Having manually import a group after Okta creates it is not ideal, so being able to manage its permissions separately would be great. In a way, similarly to fivetran_team_connector_membership, fivetran_team_group_membership and fivetran_team_user_membership.
My ideal solution would be having something like this (feel free to pick a better name 🙂):
Also, having the option of filtering by team name when using data "fivetran_teams", or using team name instead of id when using data "fivetran_team" would be incredibly useful as well.
Many thanks!
The text was updated successfully, but these errors were encountered:
I am pushing Fivetran teams from Okta and would like to be able to manage the permissions they have (on an account level), with Terraform.
At the moment I see I can create teams, and manage their account role, like this:
However, that is forcing me to import the group if Okta has already created it. Otherwise, it tries to create a new one.
Having manually import a group after Okta creates it is not ideal, so being able to manage its permissions separately would be great. In a way, similarly to
fivetran_team_connector_membership
,fivetran_team_group_membership
andfivetran_team_user_membership
.My ideal solution would be having something like this (feel free to pick a better name 🙂):
Also, having the option of filtering by team name when using
data "fivetran_teams"
, or using team name instead of id when usingdata "fivetran_team"
would be incredibly useful as well.Many thanks!
The text was updated successfully, but these errors were encountered: