yandex_dns_firewall_iam_binding (Resource)
Allows creation and management of a single binding within IAM policy for an existing dns_firewall.
Warning
Warning: This resource is authoritative for the given role on the target dns_firewall and manages the complete set of its members. When you change or delete yandex_dns_firewall_iam_binding, the role may be removed from other subjects on the dns_firewall as well — including subjects granted outside of this resource (via the corresponding *_iam_member resource, the management console, CLI or API). Those subjects are not tracked in the Terraform state, so a plain terraform plan does not list them. Be careful.
Example usage
//
// Create a new DNS Firewall and new IAM Binding for it.
//
resource "yandex_dns_firewall" "fw1" {
name = "my-firewall"
}
resource "yandex_dns_firewall_iam_binding" "fw-editor" {
dns_firewall_id = yandex_dns_firewall.fw1.id
role = "dns.firewallEditor"
members = ["userAccount:foo_user_id"]
}
Arguments & Attributes Reference
dns_firewall_id(Required)(String). The ID of thedns_firewallto attach the policy to.id(String). The ID of this resource.members(Required)(Set Of String). An array of identities that will be granted the privilege in therole. Each entry can have one of the following values:
- userAccount:{user_id}: A unique user ID that represents a specific Yandex account.
- serviceAccount:{service_account_id}: A unique service account ID.
- federatedUser:{federated_user_id}: A unique federated user ID.
- federatedUser:{federated_user_id}:: A unique SAML federation user account ID.
- group:{group_id}: A unique group ID.
- system:group:federation:{federation_id}:users: All users in federation.
- system:group:organization:{organization_id}:users: All users in organization.
- system:allAuthenticatedUsers: All authenticated users.
- system:allUsers: All users, including unauthenticated ones.
Warning
for more information about system groups, see Cloud Documentation.
role(Required)(String). The role that should be assigned. Only one yandex_dns_firewall_iam_binding can be used per role.sleep_after(Number). For test purposes, to compensate IAM operations delay
Import
The resource can be imported by using their resource ID. For getting it you can use Yandex Cloud Web Console or Yandex Cloud CLI.
# terraform import yandex_dns_firewall_iam_binding.<resource Name> "dns_firewall_id,dns.viewer"
terraform import yandex_dns_firewall_iam_binding.viewer "dns7f**********dkhh6,dns.viewer"