Update acc-tests V2

.github/workflows/ci.yml

@@ -7,7 +7,7 @@ on:
   pull_request:
     branches:
       - main
-      - fix/update-acctests
+      - "hotfix/**"
     paths-ignore:
        - 'README.md'
 
@@ -16,7 +16,8 @@ on:
       - 'README.md'
     branches:
       - main
-      - fix/update-acctests
+      - fix/update-acctests-v2
+
 
 # Ensures only 1 action runs per PR and previous is canceled on new trigger
 concurrency:
@@ -126,7 +127,8 @@ jobs:
       fail-fast: false
       matrix:
         terraform:
-          - '1.3.*'
+          - '1.4.*'
+          - '1.5.*'
           - 'latest'
     steps:
 

docs/data-sources/connectors.md

@@ -13,7 +13,14 @@ Connectors provide connectivity to Remote Networks. For more information, see Tw
 ## Example Usage
 
 ```terraform
-data "twingate_connectors" "all" {}
+data "twingate_connectors" "all" {
+  name = "<your connector's name>"
+  #  name_regexp = "<regular expression of connector name>"
+  #  name_contains = "<a string in the connector name>"
+  #  name_exclude = "<your connector's name to exclude>"
+  #  name_prefix = "<prefix of connector name>"
+  #  name_suffix = "<suffix of connector name>"
+}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -22,6 +29,12 @@ data "twingate_connectors" "all" {}
 ### Optional
 
 - `connectors` (Attributes List) List of Connectors (see [below for nested schema](#nestedatt--connectors))
+- `name` (String) Returns only connectors that exactly match this name. If no options are passed it will return all connectors. Only one option can be used at a time.
+- `name_contains` (String) Match when the value exist in the name of the connector.
+- `name_exclude` (String) Match when the value does not exist in the name of the connector.
+- `name_prefix` (String) The name of the connector must start with the value.
+- `name_regexp` (String) The regular expression match of the name of the connector.
+- `name_suffix` (String) The name of the connector must end with the value.
 
 ### Read-Only
 

docs/data-sources/groups.md

@@ -15,6 +15,11 @@ Groups are how users are authorized to access Resources. For more information, s
 ```terraform
 data "twingate_groups" "foo" {
   name = "<your group's name>"
+  #  name_regexp = "<regular expression of group name>"
+  #  name_contains = "<a string in the group name>"
+  #  name_exclude = "<your group's name to exclude>"
+  #  name_prefix = "<prefix of resource name>"
+  #  name_suffix = "<suffix of resource name>"
 }
 
 # Group names are not constrained to be unique within Twingate,
@@ -28,8 +33,13 @@ data "twingate_groups" "foo" {
 
 - `groups` (Attributes List) List of Groups (see [below for nested schema](#nestedatt--groups))
 - `is_active` (Boolean) Returns only Groups matching the specified state.
-- `name` (String) Returns only Groups that exactly match this name.
-- `type` (String) Returns only Groups of the specified type (valid: `MANUAL`, `SYNCED`, `SYSTEM`).
+- `name` (String) Returns only groups that exactly match this name. If no options are passed it will return all resources. Only one option can be used at a time.
+- `name_contains` (String) Match when the value exist in the name of the group.
+- `name_exclude` (String) Match when the value does not exist in the name of the group.
+- `name_prefix` (String) The name of the group must start with the value.
+- `name_regexp` (String) The regular expression match of the name of the group.
+- `name_suffix` (String) The name of the group must end with the value.
+- `types` (Set of String) Returns groups that match a list of types. valid types: `MANUAL`, `SYNCED`, `SYSTEM`.
 
 ### Read-Only
 

docs/data-sources/remote_networks.md

@@ -19,6 +19,15 @@ data "twingate_remote_networks" "all" {}
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
+### Optional
+
+- `name` (String) Returns only remote networks that exactly match this name. If no options are passed it will return all remote networks. Only one option can be used at a time.
+- `name_contains` (String) Match when the value exist in the name of the remote network.
+- `name_exclude` (String) Match when the value does not exist in the name of the remote network.
+- `name_prefix` (String) The name of the remote network must start with the value.
+- `name_regexp` (String) The regular expression match of the name of the remote network.
+- `name_suffix` (String) The name of the remote network must end with the value.
+
 ### Read-Only
 
 - `id` (String) The ID of this resource.
@@ -27,8 +36,11 @@ data "twingate_remote_networks" "all" {}
 <a id="nestedatt--remote_networks"></a>
 ### Nested Schema for `remote_networks`
 
+Optional:
+
+- `name` (String) The name of the Remote Network.
+
 Read-Only:
 
 - `id` (String) The ID of the Remote Network.
 - `location` (String) The location of the Remote Network. Must be one of the following: AWS, AZURE, GOOGLE_CLOUD, ON_PREMISE, OTHER.
-- `name` (String) The name of the Remote Network

docs/data-sources/resources.md

@@ -15,6 +15,11 @@ Resources in Twingate represent servers on the private network that clients can
 ```terraform
 data "twingate_resources" "foo" {
   name = "<your resource's name>"
+  #  name_regexp = "<regular expression of resource name>"
+  #  name_contains = "<a string in the resource name>"
+  #  name_exclude = "<your resource's name to exclude>"
+  #  name_prefix = "<prefix of resource name>"
+  #  name_suffix = "<suffix of resource name>"
 }
 
 # Resource names are not constrained to be unique within Twingate,
@@ -24,9 +29,14 @@ data "twingate_resources" "foo" {
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
-### Required
+### Optional
 
-- `name` (String) The name of the Resource
+- `name` (String) Returns only resources that exactly match this name. If no options are passed it will return all resources. Only one option can be used at a time.
+- `name_contains` (String) Match when the value exist in the name of the resource.
+- `name_exclude` (String) Match when the value does not exist in the name of the resource.
+- `name_prefix` (String) The name of the resource must start with the value.
+- `name_regexp` (String) The regular expression match of the name of the resource.
+- `name_suffix` (String) The name of the resource must end with the value.
 
 ### Read-Only
 

docs/data-sources/security_policies.md

@@ -13,14 +13,27 @@ Security Policies are defined in the Twingate Admin Console and determine user a
 ## Example Usage
 
 ```terraform
-data "twingate_security_policies" "all" {}
+data "twingate_security_policies" "all" {
+  name = "<your security policy's name>"
+  #  name_regexp = "<regular expression of security policy name>"
+  #  name_contains = "<a string in the security policy name>"
+  #  name_exclude = "<your security policy's name to exclude>"
+  #  name_prefix = "<prefix of security policy name>"
+  #  name_suffix = "<suffix of security policy name>"
+}
 ```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
 ### Optional
 
+- `name` (String) Returns only security policies that exactly match this name. If no options are passed it will return all security policies. Only one option can be used at a time.
+- `name_contains` (String) Match when the value exist in the name of the security policy.
+- `name_exclude` (String) Match when the value does not exist in the name of the security policy.
+- `name_prefix` (String) The name of the security policy must start with the value.
+- `name_regexp` (String) The regular expression match of the name of the security policy.
+- `name_suffix` (String) The name of the security policy must end with the value.
 - `security_policies` (Attributes List) (see [below for nested schema](#nestedatt--security_policies))
 
 ### Read-Only

docs/data-sources/service_accounts.md

@@ -15,6 +15,11 @@ Service Accounts offer a way to provide programmatic, centrally-controlled, and
 ```terraform
 data "twingate_service_accounts" "foo" {
   name = "<your service account's name>"
+  #  name_regexp = "<regular expression of service account name>"
+  #  name_contains = "<a string in the service account name>"
+  #  name_exclude = "<your service account's name to exclude>"
+  #  name_prefix = "<prefix of service account name>"
+  #  name_suffix = "<suffix of service account name>"
 }
 ```
 
@@ -23,7 +28,12 @@ data "twingate_service_accounts" "foo" {
 
 ### Optional
 
-- `name` (String) Filter results by the name of the Service Account.
+- `name` (String) Returns only service accounts that exactly match this name. If no options are passed it will return all service accounts. Only one option can be used at a time.
+- `name_contains` (String) Match when the value exist in the name of the service account.
+- `name_exclude` (String) Match when the value does not exist in the name of the service account.
+- `name_prefix` (String) The name of the service account must start with the value.
+- `name_regexp` (String) The regular expression match of the name of the service account.
+- `name_suffix` (String) The name of the service account must end with the value.
 
 ### Read-Only
 

docs/data-sources/user.md

@@ -29,7 +29,6 @@ data "twingate_user" "foo" {
 
 - `email` (String) The email address of the User
 - `first_name` (String) The first name of the User
-- `is_admin` (Boolean, Deprecated) Indicates whether the User is an admin
 - `last_name` (String) The last name of the User
 - `role` (String) Indicates the User's role. Either ADMIN, DEVOPS, SUPPORT, or MEMBER
 - `type` (String) Indicates the User's type. Either MANUAL or SYNCED.

docs/data-sources/users.md

@@ -13,12 +13,57 @@ Users in Twingate can be given access to Twingate Resources and may either be ad
 ## Example Usage
 
 ```terraform
-data "twingate_users" "all" {}
+data "twingate_users" "all" {
+  #  email = "<your user's email>"
+  #  email_regexp = "<regular expression of user email>"
+  #  email_contains = "<a string in the user email>"
+  #  email_exclude = "<your user's email to exclude>"
+  #  email_prefix = "<prefix of user email>"
+  #  email_suffix = "<suffix of user email>"
+
+  #  first_name = "<your user's first name>"
+  #  first_name_regexp = "<regular expression of user first name>"
+  #  first_name_contains = "<a string in the user first name>"
+  #  first_name_exclude = "<your user's first name to exclude>"
+  #  first_name_prefix = "<prefix of user first name>"
+  #  first_name_suffix = "<suffix of user first name>"
+
+  #  last_name = "<your user's last name>"
+  #  last_name_regexp = "<regular expression of user last name>"
+  #  last_name_contains = "<a string in the user last name>"
+  #  last_name_exclude = "<your user's last name to exclude>"
+  #  last_name_prefix = "<prefix of user last name>"
+  #  last_name_suffix = "<suffix of user last name>"
+
+  #  roles = ["ADMIN", "DEVOPS", "SUPPORT", "MEMBER"]
+}
 ```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema
 
+### Optional
+
+- `email` (String) Returns only users that exactly match this email.
+- `email_contains` (String) Match when the value exist in the email of the user.
+- `email_exclude` (String) Match when the value does not exist in the email of the user.
+- `email_prefix` (String) The email of the user must start with the value.
+- `email_regexp` (String) The regular expression match of the email of the user.
+- `email_suffix` (String) The email of the user must end with the value.
+- `first_name` (String) Returns only users that exactly match the first name.
+- `first_name_contains` (String) Match when the value exist in the first name of the user.
+- `first_name_exclude` (String) Match when the value does not exist in the first name of the user.
+- `first_name_prefix` (String) The first name of the user must start with the value.
+- `first_name_regexp` (String) The regular expression match of the first name of the user.
+- `first_name_suffix` (String) The first name of the user must end with the value.
+- `last_name` (String) Returns only users that exactly match the last name.
+- `last_name_contains` (String) Match when the value exist in the last name of the user.
+- `last_name_exclude` (String) Match when the value does not exist in the last name of the user.
+- `last_name_prefix` (String) The last name of the user must start with the value.
+- `last_name_regexp` (String) The regular expression match of the last name of the user.
+- `last_name_suffix` (String) The last name of the user must end with the value.
+- `roles` (Set of String) Returns users that match a list of roles. Valid roles: `ADMIN`, `DEVOPS`, `SUPPORT`, `MEMBER`.
+
 ### Read-Only
 
 - `id` (String) The ID of this resource.
@@ -32,7 +77,6 @@ Read-Only:
 - `email` (String) The email address of the User
 - `first_name` (String) The first name of the User
 - `id` (String) The ID of the User
-- `is_admin` (Boolean, Deprecated) Indicates whether the User is an admin
 - `last_name` (String) The last name of the User
 - `role` (String) Indicates the User's role. Either ADMIN, DEVOPS, SUPPORT, or MEMBER.
 - `type` (String) Indicates the User's type. Either MANUAL or SYNCED.

docs/guides/migration-v1-to-v2-guide.md

@@ -0,0 +1,73 @@
+---
+subcategory: "migration"
+page_title: "v1 to v2 Migration Guide"
+description: |-
+This document covers how to migrate from v1 to v2 of the Twingate Terraform provider.
+---
+
+# Migration Guide
+j
+This guide covers how to migrate from v1 to v2 of the Twingate Terraform provider. Migration needs to be done for the following objects:
+- Resources
+    - `twingate_resource`
+- Data sources
+    - `twingate_user`
+    - `twingate_users`
+
+## Migrating Resources
+
+The `protocols` attribute in the `twingate_resource` Resource has been changed from a block to an object.
+
+In v1, the following was valid:
+
+```terraform
+resource "twingate_resource" "resource" {
+  name = "resource"
+  address = "internal.int"
+  remote_network_id = twingate_remote_network.aws_network.id
+
+  protocols {
+    allow_icmp = true
+    tcp {
+      policy = "RESTRICTED"
+      ports = ["80", "82-83"]
+    }
+    udp {
+      policy = "ALLOW_ALL"
+    }
+  }
+}
+```
+
+The `protocols`, `tcp` and `udp` attributes were blocks and not objects. In v2, these are now objects:
+
+```
+protocols {   ->   protocols = {
+tcp {         ->   tcp = {
+udp {         ->   udp = {
+```
+
+In v2, the above resource needs to be rewritten like this:
+
+```terraform
+resource "twingate_resource" "resource" {
+  name = "resource"
+  address = "internal.int"
+  remote_network_id = twingate_remote_network.aws_network.id
+
+  protocols = {
+    allow_icmp = true
+    tcp = {
+      policy = "RESTRICTED"
+      ports = ["80", "82-83"]
+    }
+    udp = {
+      policy = "ALLOW_ALL"
+    }
+  }
+}
+```
+
+## Migrating data sources
+
+The attribute `is_admin` has been removed from the `twingate_user` and `twingate_users` data sources. Similar information is now available via the [`role` attribute](https://registry.terraform.io/providers/Twingate/twingate/latest/docs/data-sources/users#role).

docs/resources/connector.md

@@ -24,6 +24,7 @@ resource "twingate_remote_network" "aws_network" {
 
 resource "twingate_connector" "aws_connector" {
   remote_network_id = twingate_remote_network.aws_network.id
+  status_updates_enabled = true
 }
 ```
 
@@ -37,7 +38,7 @@ resource "twingate_connector" "aws_connector" {
 ### Optional
 
 - `name` (String) Name of the Connector, if not provided one will be generated.
-- `status_updates_enabled` (Boolean) Determines whether status notifications are enabled for the Connector.
+- `status_updates_enabled` (Boolean) Determines whether status notifications are enabled for the Connector. Default is `true`.
 
 ### Read-Only