Update dependency hashicorp/terraform-provider-hcp to v0.66.0 (#22)

Signed-off-by: tflibsonnet-ci <[email protected]>
Co-authored-by: renovate[bot] <renovate[bot]@users.noreply.github.com>

0.x/_gen/data/aws_network_peering.libsonnet

@@ -2,7 +2,7 @@ local tf = (import 'github.com/tf-libsonnet/core/main.libsonnet');
 local d = (import 'github.com/jsonnet-libs/docsonnet/doc-util/main.libsonnet');
 {
   '#':: d.pkg(name='aws_network_peering', url='', help='`aws_network_peering` represents the `hcp_aws_network_peering` Terraform data source.\n\nThe AWS network peering data source provides information about an existing network peering between an HVN and a peer AWS VPC.\n\nThis package contains functions and utilities for setting up the data source using Jsonnet code.\n'),
-  '#new':: d.fn(help="\n`hcp.data.aws_network_peering.new` injects a new `data_hcp_aws_network_peering` Terraform `data source`\nblock into the root module document.\n\nAdditionally, this inserts a private function into the `_ref` attribute that generates references to attributes of the\nresource. For example, if you added a new instance to the root using:\n\n    # arguments omitted for brevity\n    hcp.data.aws_network_peering.new('some_id')\n\nYou can get the reference to the `id` field of the created `hcp.data.aws_network_peering` using the reference:\n\n    $._ref.data_hcp_aws_network_peering.some_id.get('id')\n\nThis is the same as directly entering `\"${ data_hcp_aws_network_peering.some_id.id }\"` as the value.\n\nNOTE: if you are chaining multiple resources together in a merge operation, you may not be able to use `super`, `self`,\nor `$` to refer to the root object. Instead, make an explicit outer object using `local`.\n\n**Args**:\n  - `dataSrcLabel` (`string`): The name label of the block.\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `peering_id` (`string`): The ID of the network peering.\n  - `project_id` (`string`): The ID of the HCP project where the network peering is located. Always matches the HVN\u0026#39;s project. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the network peering to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting data source block. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_network_peering.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n- A mixin object that injects the new data source into the root Terraform configuration.\n", args=[]),
+  '#new':: d.fn(help="\n`hcp.data.aws_network_peering.new` injects a new `data_hcp_aws_network_peering` Terraform `data source`\nblock into the root module document.\n\nAdditionally, this inserts a private function into the `_ref` attribute that generates references to attributes of the\nresource. For example, if you added a new instance to the root using:\n\n    # arguments omitted for brevity\n    hcp.data.aws_network_peering.new('some_id')\n\nYou can get the reference to the `id` field of the created `hcp.data.aws_network_peering` using the reference:\n\n    $._ref.data_hcp_aws_network_peering.some_id.get('id')\n\nThis is the same as directly entering `\"${ data_hcp_aws_network_peering.some_id.id }\"` as the value.\n\nNOTE: if you are chaining multiple resources together in a merge operation, you may not be able to use `super`, `self`,\nor `$` to refer to the root object. Instead, make an explicit outer object using `local`.\n\n**Args**:\n  - `dataSrcLabel` (`string`): The name label of the block.\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `peering_id` (`string`): The ID of the network peering.\n  - `project_id` (`string`): \nThe ID of the HCP project where the network peering is located. Always matches the HVN\u0026#39;s project.\nIf not specified, the project specified in the HCP Provider config block will be used, if configured.\nIf a project is not configured in the HCP Provider config block, the oldest project in the organization will be used. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the network peering to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting data source block. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_network_peering.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n- A mixin object that injects the new data source into the root Terraform configuration.\n", args=[]),
   new(
     dataSrcLabel,
     hvn_id,
@@ -23,7 +23,7 @@ local d = (import 'github.com/jsonnet-libs/docsonnet/doc-util/main.libsonnet');
     ),
     _meta=_meta
   ),
-  '#newAttrs':: d.fn(help='\n`hcp.data.aws_network_peering.newAttrs` constructs a new object with attributes and blocks configured for the `aws_network_peering`\nTerraform data source.\n\nUnlike [hcp.data.aws_network_peering.new](#fn-new), this function will not inject the `data source`\nblock into the root Terraform document. Instead, this must be passed in as the `attrs` argument for the\n[tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) function to build a complete block.\n\nThis is most useful when you need to preprocess the attributes with functions, conditional, or looping logic prior to\ninjecting into a complete block.\n\n**Args**:\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `peering_id` (`string`): The ID of the network peering.\n  - `project_id` (`string`): The ID of the HCP project where the network peering is located. Always matches the HVN's project. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the network peering to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting object. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_network_peering.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n  - An attribute object that can be used with [tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) to construct a new `aws_network_peering` data source into the root Terraform configuration.\n', args=[]),
+  '#newAttrs':: d.fn(help='\n`hcp.data.aws_network_peering.newAttrs` constructs a new object with attributes and blocks configured for the `aws_network_peering`\nTerraform data source.\n\nUnlike [hcp.data.aws_network_peering.new](#fn-new), this function will not inject the `data source`\nblock into the root Terraform document. Instead, this must be passed in as the `attrs` argument for the\n[tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) function to build a complete block.\n\nThis is most useful when you need to preprocess the attributes with functions, conditional, or looping logic prior to\ninjecting into a complete block.\n\n**Args**:\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `peering_id` (`string`): The ID of the network peering.\n  - `project_id` (`string`): \nThe ID of the HCP project where the network peering is located. Always matches the HVN's project.\nIf not specified, the project specified in the HCP Provider config block will be used, if configured.\nIf a project is not configured in the HCP Provider config block, the oldest project in the organization will be used. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the network peering to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting object. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_network_peering.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n  - An attribute object that can be used with [tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) to construct a new `aws_network_peering` data source into the root Terraform configuration.\n', args=[]),
   newAttrs(
     hvn_id,
     peering_id,

0.x/_gen/data/aws_transit_gateway_attachment.libsonnet

@@ -2,7 +2,7 @@ local tf = (import 'github.com/tf-libsonnet/core/main.libsonnet');
 local d = (import 'github.com/jsonnet-libs/docsonnet/doc-util/main.libsonnet');
 {
   '#':: d.pkg(name='aws_transit_gateway_attachment', url='', help='`aws_transit_gateway_attachment` represents the `hcp_aws_transit_gateway_attachment` Terraform data source.\n\nThe AWS transit gateway attachment data source provides information about an existing transit gateway attachment.\n\nThis package contains functions and utilities for setting up the data source using Jsonnet code.\n'),
-  '#new':: d.fn(help="\n`hcp.data.aws_transit_gateway_attachment.new` injects a new `data_hcp_aws_transit_gateway_attachment` Terraform `data source`\nblock into the root module document.\n\nAdditionally, this inserts a private function into the `_ref` attribute that generates references to attributes of the\nresource. For example, if you added a new instance to the root using:\n\n    # arguments omitted for brevity\n    hcp.data.aws_transit_gateway_attachment.new('some_id')\n\nYou can get the reference to the `id` field of the created `hcp.data.aws_transit_gateway_attachment` using the reference:\n\n    $._ref.data_hcp_aws_transit_gateway_attachment.some_id.get('id')\n\nThis is the same as directly entering `\"${ data_hcp_aws_transit_gateway_attachment.some_id.id }\"` as the value.\n\nNOTE: if you are chaining multiple resources together in a merge operation, you may not be able to use `super`, `self`,\nor `$` to refer to the root object. Instead, make an explicit outer object using `local`.\n\n**Args**:\n  - `dataSrcLabel` (`string`): The name label of the block.\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `project_id` (`string`): The ID of the HCP project where the transit gateway attachment is located. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `transit_gateway_attachment_id` (`string`): The user-settable name of the transit gateway attachment in HCP.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the transit gateway attachment to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting data source block. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_transit_gateway_attachment.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n- A mixin object that injects the new data source into the root Terraform configuration.\n", args=[]),
+  '#new':: d.fn(help="\n`hcp.data.aws_transit_gateway_attachment.new` injects a new `data_hcp_aws_transit_gateway_attachment` Terraform `data source`\nblock into the root module document.\n\nAdditionally, this inserts a private function into the `_ref` attribute that generates references to attributes of the\nresource. For example, if you added a new instance to the root using:\n\n    # arguments omitted for brevity\n    hcp.data.aws_transit_gateway_attachment.new('some_id')\n\nYou can get the reference to the `id` field of the created `hcp.data.aws_transit_gateway_attachment` using the reference:\n\n    $._ref.data_hcp_aws_transit_gateway_attachment.some_id.get('id')\n\nThis is the same as directly entering `\"${ data_hcp_aws_transit_gateway_attachment.some_id.id }\"` as the value.\n\nNOTE: if you are chaining multiple resources together in a merge operation, you may not be able to use `super`, `self`,\nor `$` to refer to the root object. Instead, make an explicit outer object using `local`.\n\n**Args**:\n  - `dataSrcLabel` (`string`): The name label of the block.\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `project_id` (`string`): \nThe ID of the HCP project where the transit gateway attachment is located.\nIf not specified, the project specified in the HCP Provider config block will be used, if configured.\nIf a project is not configured in the HCP Provider config block, the oldest project in the organization will be used. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `transit_gateway_attachment_id` (`string`): The user-settable name of the transit gateway attachment in HCP.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the transit gateway attachment to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting data source block. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_transit_gateway_attachment.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n- A mixin object that injects the new data source into the root Terraform configuration.\n", args=[]),
   new(
     dataSrcLabel,
     hvn_id,
@@ -23,7 +23,7 @@ local d = (import 'github.com/jsonnet-libs/docsonnet/doc-util/main.libsonnet');
     ),
     _meta=_meta
   ),
-  '#newAttrs':: d.fn(help='\n`hcp.data.aws_transit_gateway_attachment.newAttrs` constructs a new object with attributes and blocks configured for the `aws_transit_gateway_attachment`\nTerraform data source.\n\nUnlike [hcp.data.aws_transit_gateway_attachment.new](#fn-new), this function will not inject the `data source`\nblock into the root Terraform document. Instead, this must be passed in as the `attrs` argument for the\n[tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) function to build a complete block.\n\nThis is most useful when you need to preprocess the attributes with functions, conditional, or looping logic prior to\ninjecting into a complete block.\n\n**Args**:\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `project_id` (`string`): The ID of the HCP project where the transit gateway attachment is located. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `transit_gateway_attachment_id` (`string`): The user-settable name of the transit gateway attachment in HCP.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the transit gateway attachment to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting object. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_transit_gateway_attachment.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n  - An attribute object that can be used with [tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) to construct a new `aws_transit_gateway_attachment` data source into the root Terraform configuration.\n', args=[]),
+  '#newAttrs':: d.fn(help='\n`hcp.data.aws_transit_gateway_attachment.newAttrs` constructs a new object with attributes and blocks configured for the `aws_transit_gateway_attachment`\nTerraform data source.\n\nUnlike [hcp.data.aws_transit_gateway_attachment.new](#fn-new), this function will not inject the `data source`\nblock into the root Terraform document. Instead, this must be passed in as the `attrs` argument for the\n[tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) function to build a complete block.\n\nThis is most useful when you need to preprocess the attributes with functions, conditional, or looping logic prior to\ninjecting into a complete block.\n\n**Args**:\n  - `hvn_id` (`string`): The ID of the HashiCorp Virtual Network (HVN).\n  - `project_id` (`string`): \nThe ID of the HCP project where the transit gateway attachment is located.\nIf not specified, the project specified in the HCP Provider config block will be used, if configured.\nIf a project is not configured in the HCP Provider config block, the oldest project in the organization will be used. When `null`, the `project_id` field will be omitted from the resulting object.\n  - `transit_gateway_attachment_id` (`string`): The user-settable name of the transit gateway attachment in HCP.\n  - `wait_for_active_state` (`bool`): If `true`, Terraform will wait for the transit gateway attachment to reach an `ACTIVE` state before continuing. Default `false`. When `null`, the `wait_for_active_state` field will be omitted from the resulting object.\n  - `timeouts` (`obj`): Set the `timeouts` field on the resulting object. When `null`, the `timeouts` sub block will be omitted from the resulting object. When setting the sub block, it is recommended to construct the object using the [hcp.data.aws_transit_gateway_attachment.timeouts.new](#fn-timeoutsnew) constructor.\n\n**Returns**:\n  - An attribute object that can be used with [tf.withData](https://github.com/tf-libsonnet/core/tree/main/docs#fn-withdata) to construct a new `aws_transit_gateway_attachment` data source into the root Terraform configuration.\n', args=[]),
   newAttrs(
     hvn_id,
     transit_gateway_attachment_id,