mirror of
https://github.com/opentffoundation/opentf.git
synced 2026-04-20 15:01:55 -04:00
987b910828
* vendor: update gopkg.in/ns1/ns1-go.v2 * provider/ns1: Port the ns1 provider to Terraform core * docs/ns1: Document the ns1 provider * ns1: rename remaining nsone -> ns1 (#10805) * Ns1 provider (#11300) * provider/ns1: Flesh out support for meta structs. Following the structure outlined by @pashap. Using reflection to reduce copy/paste. Putting metas inside single-item lists. This is clunky, but I couldn't figure out how else to have a nested struct. Maybe the Terraform people know a better way? Inside the meta struct, all fields are always written to the state; I can't figure out how to omit fields that aren't used. This is not just verbose, it actually causes issues because you can't have both "up" and "up_feed" set). Also some minor other changes: - Add "terraform" import support to records and zones. - Create helper class StringEnum. * provider/ns1: Make fmt * provider/ns1: Remove stubbed out RecordRead (used for testing metadata change). * provider/ns1: Need to get interface that m contains from Ptr Value with Elem() * provider/ns1: Use empty string to indicate no feed given. * provider/ns1: Remove old record.regions fields. * provider/ns1: Removes redundant testAccCheckRecordState * provider/ns1: Moves account permissions logic to permissions.go * provider/ns1: Adds tests for team resource. * provider/ns1: Move remaining permissions logic to permissions.go * ns1/provider: Adds datasource.config * provider/ns1: Small clean up of datafeed resource tests * provider/ns1: removes testAccCheckZoneState in favor of explicit name check * provider/ns1: More renaming of nsone -> ns1 * provider/ns1: Comment out metadata for the moment. * Ns1 provider (#11347) * Fix the removal of empty containers from a flatmap Removal of empty nested containers from a flatmap would sometimes fail a sanity check when removed in the wrong order. This would only fail sometimes due to map iteration. There was also an off-by-one error in the prefix check which could match the incorrect keys. * provider/ns1: Adds ns1 go client through govendor. * provider/ns1: Removes unused debug line * docs/ns1: Adds docs around apikey/datasource/datafeed/team/user/record. * provider/ns1: Gets go vet green
2.8 KiB
2.8 KiB
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| ns1 | NS1: ns1_user | docs-ns1-resource-user | Provides a NS1 User resource. |
ns1_user
Provides a NS1 User resource. Creating a user sends an invitation email to the user's email address. This can be used to create, modify, and delete users.
Example Usage
resource "ns1_team" "example" {
name = "Example team"
permissions = {
dns_view_zones = false
account_manage_users = false
}
}
resource "ns1_user" "example" {
name = "Example User"
username = "example_user"
email = "user@example.com"
teams = ["${ns1_team.example.id}"]
}
Argument Reference
The following arguments are supported:
name- (Required) The free form name of the user.username- (Required) The users login name.email- (Required) The email address of the user.notify- (Required) The Whether or not to notify the user of specified events. Onlybillingis available currently.teams- (Required) The teams that the user belongs to.permissions- (Optional) The allowed permissions of the user. Permissions documented below.
Permissions (permissions) support the following:
dns_view_zones- (Optional) Whether the user can view the accounts zones.dns_manage_zones- (Optional) Whether the user can modify the accounts zones.dns_zones_allow_by_default- (Optional) If true, enable thedns_zones_allowlist, otherwise enable thedns_zones_denylist.dns_zones_allow- (Optional) List of zones that the user may access.dns_zones_deny- (Optional) List of zones that the user may not access.data_push_to_datafeeds- (Optional) Whether the user can publish to data feeds.data_manage_datasources- (Optional) Whether the user can modify data sources.data_manage_datafeeds- (Optional) Whether the user can modify data feeds.account_manage_users- (Optional) Whether the user can modify account users.account_manage_payment_methods- (Optional) Whether the user can modify account payment methods.account_manage_plan- (Optional) Whether the user can modify the account plan.account_manage_teams- (Optional) Whether the user can modify other teams in the account.account_manage_apikeys- (Optional) Whether the user can modify account apikeys.account_manage_account_settings- (Optional) Whether the user can modify account settings.account_view_activity_log- (Optional) Whether the user can view activity logs.account_view_invoices- (Optional) Whether the user can view invoices.monitoring_manage_lists- (Optional) Whether the user can modify notification lists.monitoring_manage_jobs- (Optional) Whether the user can modify monitoring jobs.monitoring_view_jobs- (Optional) Whether the user can view monitoring jobs.