v1.1.3-rc1

Deprecation Notice

The attribute is_admin is now deprecated in the user and users data sources in this release and will be removed in a future release. In order to determine whether a user is an admin, the value of the role attribute can be checked instead. Any value other than MEMBER indicates that the user is an admin.

What's Changed

Bug fixes

• This release contains only minor bug fixes.

Full Changelog: v1.1.2...v1.1.3-rc1

v1.1.2

Deprecation Notice

The attribute is_admin is now deprecated in the user and users data sources in this release and will be removed in a future release. In order to determine whether a user is an admin, the value of the role attribute can be checked instead. Any value other than MEMBER indicates that the user is an admin.

What's Changed

Enhancements

• Reduced number of provider API calls to improve performance by @vmanilo in #340

Full Changelog: v1.1.1...v1.1.2

v1.1.1

Deprecation Notice

The attribute is_admin is now deprecated in the user and users data sources in this release and will be removed in a future release. In order to determine whether a user is an admin, the value of the role attribute can be checked instead. Any value other than MEMBER indicates that the user is an admin.

What's Changed

Documentation

• Update AWS deployment guide example for changes to twingate_resource by @HotGiardiniera in #337

New Contributors

• @HotGiardiniera made their first contribution in #337

Full Changelog: v1.1.0...v1.1.1

v1.1.0

Deprecation Notice

The attribute is_admin is now deprecated in the user and users data sources in this release and will be removed in a future release. In order to determine whether a user is an admin, the value of the role attribute can be checked instead. Any value other than MEMBER indicates that the user is an admin.

What's Changed

Features

• Added a new twingate_user resource to allow managing users by @vmanilo in #323
  • Note that only limited user management functionality is available on users synced from your IdP. Social user management must be enabled for your Twingate account if you already use an IdP (see our announcement). See our documentation for more information on IdP configuration.
• The type attribute was added to the user and users data sources, which indicates whether the user is synced from an IdP or was manually invited by @vmanilo in #320

Bug Fixes

• Resolved a paging issue affecting operations on larger groups in Twingate by @vmanilo in #330

Full Changelog: v1.0.0...v1.1.0

v1.1.0-rc1

Deprecation Notice

The attribute is_admin is now deprecated in the user and users data sources in this release and will be removed in a future release. In order to determine whether a user is an admin, the value of the role attribute can be checked instead. Any value other than MEMBER indicates that the user is an admin.

What's Changed

Features

• Added a new twingate_user resource to allow managing users by @vmanilo in #323
  • Note that only limited user management functionality is available on users synced from your IdP. Social user management must be enabled for your Twingate account if you already use an IdP (see our announcement). See our documentation for more information on IdP configuration.
• The type attribute was added to the user and users data sources, which indicates whether the user is synced from an IdP or was manually invited by @vmanilo in #320

Bug Fixes

• Resolved a paging issue affecting operations on larger groups in Twingate by @vmanilo in #330

Full Changelog: v1.0.0...v1.1.0-rc1

v1.0.0

Breaking change notice

• As of v1.0.0, the group_ids argument is no longer supported within the twingate_resource resource. This functionality has been replaced by a new access block argument, which we will continue to enhance in the future. The group_ids argument was marked as deprecated in v0.3.0.
• The example below demonstrates how to migrate to the new access block for existing Terraform configurations.

resource “twingate_resource” “resource” {
  name = “network”
  address = “internal.int”
  remote_network_id = twingate_remote_network.aws_network.id
  # This argument is now invalid outside of the new access block
  # group_ids = [twingate_group.aws.id]
  access {
    group_ids = [twingate_group.aws.id]
  }
}

What's Changed

Breaking

• Removed the deprecated group_ids argument in twingate_resource by @vmanilo in #290

Features

• Added optional alias argument to twingate_resource resource by @vmanilo in #316

Full Changelog: v0.3.3...v1.0.0

v1.0.0-rc1

Breaking change notice

• As of v1.0.0, the group_ids argument is no longer supported within the twingate_resource resource. This functionality has been replaced by a new access block argument, which we will continue to enhance in the future. The group_ids argument was marked as deprecated in v0.3.0.
• The example below demonstrates how to migrate to the new access block for existing Terraform configurations.

resource “twingate_resource” “resource” {
  name = “network”
  address = “internal.int”
  remote_network_id = twingate_remote_network.aws_network.id
  # This argument is now invalid outside of the new access block
  # group_ids = [twingate_group.aws.id]
  access {
    group_ids = [twingate_group.aws.id]
  }
}

What's Changed

Breaking

• Removed the deprecated group_ids argument in twingate_resource by @vmanilo in #290

Full Changelog: v0.3.3...v1.0.0-rc1

v0.3.3

Deprecation notice

• As of v0.3.0, the group_ids argument is now deprecated in the twingate_resource resource. This functionality has been replaced by a new access block argument in this release, which we will continue to enhance in the future. The deprecated group_ids argument continues to work for now, so existing Terraform configurations will not be impacted, but this argument will be removed in a future release.
• We encourage you to move to the new access block configuration as soon as possible. The example below demonstrates how to migrate to the new access block for existing Terraform configurations.

resource “twingate_resource” “resource” {
  name = “network”
  address = “internal.int”
  remote_network_id = twingate_remote_network.aws_network.id
  # This argument is now deprecated outside of the new access block
  # group_ids = [twingate_group.aws.id]
  access {
    group_ids = [twingate_group.aws.id]
  }
}

What's Changed

Features

• Added the ability to set a security policy ID (via the security_policy_id argument) to the twingate_group resource by @vmanilo in #262
• Added the security_policy_id value to the twingate_group data source output by @vmanilo in #270
• Added the ability to assign users from the twingate_user and twingate_users data sources to twingate_group resources by @vmanilo in #266
• Added the ability to control Connector status updates via the status_updates_enabled argument in the twingate_connector resource by @vmanilo in #293

Full Changelog: v0.3.2...v0.3.3

v0.3.2

Deprecation notice

• As of v0.3.0, the group_ids argument is now deprecated in the twingate_resource resource. This functionality has been replaced by a new access block argument in this release, which we will continue to enhance in the future. The deprecated group_ids argument continues to work for now, so existing Terraform configurations will not be impacted, but this argument will be removed in a future release.
• We encourage you to move to the new access block configuration as soon as possible. The example below demonstrates how to migrate to the new access block for existing Terraform configurations.

resource “twingate_resource” “resource” {
  name = “network”
  address = “internal.int”
  remote_network_id = twingate_remote_network.aws_network.id
  # This argument is now deprecated outside of the new access block
  # group_ids = [twingate_group.aws.id]
  access {
    group_ids = [twingate_group.aws.id]
  }
}

What's Changed

Bug fixes

• Resolved an issue where the is_visible and is_browser_shortcut_enabled arguments in the twingate_resource resource were not working as intended by @vmanilo in #285
• Resolved a minor issue affecting retry logic for invalid provider configuration by @vmanilo in #283

Full Changelog: v0.3.1...v0.3.2

v0.3.1

Deprecation notice

• As of v0.3.0, the group_ids argument is now deprecated in the twingate_resource resource. This functionality has been replaced by a new access block argument in this release, which we will continue to enhance in the future. The deprecated group_ids argument continues to work for now, so existing Terraform configurations will not be impacted, but this argument will be removed in a future release.
• We encourage you to move to the new access block configuration as soon as possible. The example below demonstrates how to migrate to the new access block for existing Terraform configurations.

resource “twingate_resource” “resource” {
  name = “network”
  address = “internal.int”
  remote_network_id = twingate_remote_network.aws_network.id
  # This argument is now deprecated outside of the new access block
  # group_ids = [twingate_group.aws.id]
  access {
    group_ids = [twingate_group.aws.id]
  }
}

What’s Changed

Enhancements

• Improved resource is_authoritative argument behavior when upgrading from a provider version prior to v0.3.0 to v0.3.1 or later by @vmanilo in #277

Full Changelog: v0.3.0...v0.3.1