v0.3.0

Deprecation notice

• 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

• Added a new access block argument to the twingate_resource resource. This new block allows assigning both Service Accounts and Groups to Resources and will be extended in the future to match the evolution of the core product. Authored by @vmanilo in #249
  • Note: Using the group_ids argument outside of the access block is now deprecated and will be fully removed in a future release. We encourage you to move to the new access block syntax as soon as possible.

Full Changelog: v0.2.5...v0.3.0

v0.2.5

What's Changed

Bug fixes

• Resolved an issue that caused incorrect plan rollout on twingate_resource Resource visibility flags by @vmanilo in #260

Full Changelog: v0.2.4...v0.2.5

v0.2.4

What's Changed

Enhancements

• Added a new twingate_service_accounts data source by @vmanilo in #226
• Added new twingate_security_policy and twingate_security_policies data sources by @vmanilo in #229
• Added a new twingate_remote_networks data source by @vmanilo in #255
• Added new Twingate Resource visibility options to twingate_resource by @vmanilo in #253

Full Changelog: v0.2.3...v0.2.4

v0.2.3

What's Changed

Bug fixes and improvements

• Resolved an issue that prevented the location being updated for existing Remote Networks by @vmanilo in #243

Full Changelog: v0.2.2...v0.2.3

v0.2.2

What's Changed

Enhancements

• Created a new twingate_service_account resource for Twingate Service Accounts by @vmanilo in #219
• Created a new twingate_service_account_key resource for Twingate Service Account keys by @vmanilo in #220
• Added a location property to the twingate_remote_network resource and data sources to allow setting Twingate Remote Network location by @vmanilo in #232
• Modified the behavior of the provider client initialization so that an API key is only required in the provider configuration if calls must be made to Twingate by @vmanilo in #233

Bug fixes and improvements

• Resolved an issue where not all groups were returned when applying changes for a twingate_resource resource where more than 50 groups were assigned to the Twingate Resource by @vmanilo in #207
• Resolved an issue that prevented the twingate_connectors data source from returning all Connectors by @vmanilo in #215

Notes

• Twingate Resource assignment to the twingate_service_account resource is not yet possible in this release. This will be released shortly in an upcoming release. Please follow issue #241 for updates.

Full Changelog: v0.2.1...v0.2.2

v0.2.1

What's Changed

Bug fixes and improvements

• Optimized connector_resource creation API operations by @vmanilo in #187
• Optimized group_resource API operations by @vmanilo in #193
• Optimized remote_network resource API operations by @vmanilo in #195
• Optimized connector_resource API operations by @vmanilo in #194
• Optimized resource_resource API operations by @vmanilo in #196
• Migrated token verification to v4 API by @ekampf in #200

Full Changelog: v0.2.0...v0.2.1

v0.2.0

What's Changed

Enhancements

• Added support for a new twingate_user data source by @vmanilo in #126
• Added support for a new twingate_users data source by @vmanilo in #127
• Added the ability to look up a twingate_remote_network data source by remote network name by @vmanilo in #175

Bug fixes and improvements

• Fixed documentation generator for nested schema objects in data sources by @vmanilo in #157
• Increase DefaultHTTPMaxRetry to 10 by @ekampf in #183
• Small documentation update by @ekampf in #156

Full Changelog: v0.1.10...v0.2.0

v0.1.10

What's Changed

Bug fixes and improvements

• Resolved an issue where Twingate resource imports would fail to correctly configure existing port restrictions by @vmanilo in #151

Full Changelog: v0.1.9...v0.1.10

v0.1.9

What's Changed

Enhancements

• Added support for a new twingate_group data source by @vmanilo in #116
• Added support for a new twingate_groups data source by @vmanilo in #117
• Added support for a new twingate_resource data source by @vmanilo in #124
• Added support for a new twingate_resources data source by @vmanilo in #125
• Added support for a new twingate_connector data source by @vmanilo in #128
• Added support for a new twingate_connectors data source by @vmanilo in #129

Bug fixes and improvements

• Resolved an issue where the provider would not set a resource to active after it was set to inactive outside of the provider by @vmanilo in #131
• Resolved an issue where resources were not recreated after being deleted outside of the provider by @vmanilo in #135

Full Changelog: v0.1.8...v0.1.9

v0.1.8

What's Changed

Enhancements

• Added support for a new twingate_remote_network data source by @vmanilo in #112

Bug fixes and improvements

• Fixed an issue where the same set of ports defined differently would unnecessarily trigger Terraform apply changes by @vmanilo in #123

Full Changelog: v0.1.7...v0.1.8