@pulumi/confluentcloud 2.27.0-alpha.1746733902 → 2.27.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/apiKey.d.ts +21 -21
- package/apiKey.js +21 -21
- package/clusterLink.d.ts +4 -4
- package/clusterLink.js +4 -4
- package/connector.d.ts +14 -14
- package/connector.js +14 -14
- package/environment.d.ts +21 -21
- package/environment.js +21 -21
- package/getPrivateLinkAttachment.d.ts +4 -4
- package/getPrivateLinkAttachment.js +4 -4
- package/getPrivateLinkAttachmentConnection.d.ts +4 -4
- package/getPrivateLinkAttachmentConnection.js +4 -4
- package/getProviderIntegration.d.ts +2 -2
- package/getProviderIntegration.js +2 -2
- package/kafkaAcl.d.ts +14 -14
- package/kafkaAcl.js +14 -14
- package/kafkaCluster.d.ts +22 -22
- package/kafkaCluster.js +22 -22
- package/kafkaMirrorTopic.d.ts +2 -2
- package/kafkaMirrorTopic.js +2 -2
- package/kafkaTopic.d.ts +21 -21
- package/kafkaTopic.js +21 -21
- package/network.d.ts +15 -15
- package/network.js +15 -15
- package/package.json +2 -2
- package/peering.d.ts +9 -9
- package/peering.js +9 -9
- package/privateLinkAccess.d.ts +6 -6
- package/privateLinkAccess.js +6 -6
- package/privateLinkAttachment.d.ts +2 -2
- package/privateLinkAttachment.js +2 -2
- package/privateLinkAttachmentConnection.d.ts +2 -2
- package/privateLinkAttachmentConnection.js +2 -2
- package/providerIntegration.d.ts +1 -1
- package/providerIntegration.js +1 -1
- package/serviceAccount.d.ts +21 -21
- package/serviceAccount.js +21 -21
- package/tableflowTopic.d.ts +4 -4
- package/tableflowTopic.js +4 -4
- package/transitGatewayAttachment.d.ts +1 -1
- package/transitGatewayAttachment.js +1 -1
package/apiKey.d.ts
CHANGED
|
@@ -44,27 +44,27 @@ import * as outputs from "./types/output";
|
|
|
44
44
|
* ## Getting Started
|
|
45
45
|
*
|
|
46
46
|
* The following end-to-end examples might help to get started with `confluentcloud.ApiKey` resource:
|
|
47
|
-
* *
|
|
48
|
-
* *
|
|
49
|
-
* *
|
|
50
|
-
* *
|
|
51
|
-
* *
|
|
52
|
-
* *
|
|
53
|
-
* *
|
|
54
|
-
* *
|
|
55
|
-
* *
|
|
56
|
-
* *
|
|
57
|
-
* *
|
|
58
|
-
* *
|
|
59
|
-
* *
|
|
60
|
-
* *
|
|
61
|
-
* *
|
|
62
|
-
* *
|
|
63
|
-
* *
|
|
64
|
-
* *
|
|
65
|
-
* *
|
|
66
|
-
* *
|
|
67
|
-
* *
|
|
47
|
+
* * basic-kafka-acls: _Basic_ Kafka cluster with authorization using ACLs
|
|
48
|
+
* * basic-kafka-acls-with-alias: _Basic_ Kafka cluster with authorization using ACLs
|
|
49
|
+
* * standard-kafka-acls: _Standard_ Kafka cluster with authorization using ACLs
|
|
50
|
+
* * standard-kafka-rbac: _Standard_ Kafka cluster with authorization using RBAC
|
|
51
|
+
* * dedicated-public-kafka-acls: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using ACLs
|
|
52
|
+
* * dedicated-public-kafka-rbac: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using RBAC
|
|
53
|
+
* * dedicated-privatelink-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
54
|
+
* * dedicated-privatelink-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using RBAC
|
|
55
|
+
* * dedicated-privatelink-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using RBAC
|
|
56
|
+
* * dedicated-privatelink-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
57
|
+
* * dedicated-private-service-connect-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using ACLs
|
|
58
|
+
* * dedicated-private-service-connect-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using RBAC
|
|
59
|
+
* * dedicated-vnet-peering-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using ACLs
|
|
60
|
+
* * dedicated-vnet-peering-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using RBAC
|
|
61
|
+
* * dedicated-vpc-peering-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using ACLs
|
|
62
|
+
* * dedicated-vpc-peering-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using RBAC
|
|
63
|
+
* * dedicated-vpc-peering-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using ACLs
|
|
64
|
+
* * dedicated-vpc-peering-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using RBAC
|
|
65
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using ACLs
|
|
66
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using RBAC
|
|
67
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
68
68
|
*
|
|
69
69
|
* ## Import
|
|
70
70
|
*
|
package/apiKey.js
CHANGED
|
@@ -48,27 +48,27 @@ const utilities = require("./utilities");
|
|
|
48
48
|
* ## Getting Started
|
|
49
49
|
*
|
|
50
50
|
* The following end-to-end examples might help to get started with `confluentcloud.ApiKey` resource:
|
|
51
|
-
* *
|
|
52
|
-
* *
|
|
53
|
-
* *
|
|
54
|
-
* *
|
|
55
|
-
* *
|
|
56
|
-
* *
|
|
57
|
-
* *
|
|
58
|
-
* *
|
|
59
|
-
* *
|
|
60
|
-
* *
|
|
61
|
-
* *
|
|
62
|
-
* *
|
|
63
|
-
* *
|
|
64
|
-
* *
|
|
65
|
-
* *
|
|
66
|
-
* *
|
|
67
|
-
* *
|
|
68
|
-
* *
|
|
69
|
-
* *
|
|
70
|
-
* *
|
|
71
|
-
* *
|
|
51
|
+
* * basic-kafka-acls: _Basic_ Kafka cluster with authorization using ACLs
|
|
52
|
+
* * basic-kafka-acls-with-alias: _Basic_ Kafka cluster with authorization using ACLs
|
|
53
|
+
* * standard-kafka-acls: _Standard_ Kafka cluster with authorization using ACLs
|
|
54
|
+
* * standard-kafka-rbac: _Standard_ Kafka cluster with authorization using RBAC
|
|
55
|
+
* * dedicated-public-kafka-acls: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using ACLs
|
|
56
|
+
* * dedicated-public-kafka-rbac: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using RBAC
|
|
57
|
+
* * dedicated-privatelink-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
58
|
+
* * dedicated-privatelink-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using RBAC
|
|
59
|
+
* * dedicated-privatelink-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using RBAC
|
|
60
|
+
* * dedicated-privatelink-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
61
|
+
* * dedicated-private-service-connect-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using ACLs
|
|
62
|
+
* * dedicated-private-service-connect-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using RBAC
|
|
63
|
+
* * dedicated-vnet-peering-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using ACLs
|
|
64
|
+
* * dedicated-vnet-peering-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using RBAC
|
|
65
|
+
* * dedicated-vpc-peering-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using ACLs
|
|
66
|
+
* * dedicated-vpc-peering-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using RBAC
|
|
67
|
+
* * dedicated-vpc-peering-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using ACLs
|
|
68
|
+
* * dedicated-vpc-peering-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using RBAC
|
|
69
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using ACLs
|
|
70
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using RBAC
|
|
71
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
72
72
|
*
|
|
73
73
|
* ## Import
|
|
74
74
|
*
|
package/clusterLink.d.ts
CHANGED
|
@@ -54,10 +54,10 @@ import * as outputs from "./types/output";
|
|
|
54
54
|
* ## Getting Started
|
|
55
55
|
*
|
|
56
56
|
* The following end-to-end examples might help to get started with `confluentcloud.ClusterLink` resource:
|
|
57
|
-
* *
|
|
58
|
-
* *
|
|
59
|
-
* *
|
|
60
|
-
* *
|
|
57
|
+
* * destination-initiated-cluster-link-rbac: An example of setting up a _destination_ initiated cluster link with a mirror topic
|
|
58
|
+
* * source-initiated-cluster-link-rbac: An example of setting up a _source_ initiated cluster link with a mirror topic
|
|
59
|
+
* * regular-bidirectional-cluster-link-rbac: An example of setting up a bidirectional cluster link with 2 mirror topics
|
|
60
|
+
* * advanced-bidirectional-cluster-link-rbac: An example of setting up a bidirectional cluster link with 2 mirror topics ([advanced option](https://docs.confluent.io/cloud/current/multi-cloud/cluster-linking/cluster-links-cc.html#create-a-cluster-link-in-bidirectional-mode))
|
|
61
61
|
*
|
|
62
62
|
* See [Cluster Linking on Confluent Cloud](https://docs.confluent.io/cloud/current/multi-cloud/cluster-linking/index.html) to learn more about Cluster Linking on Confluent Cloud.
|
|
63
63
|
*
|
package/clusterLink.js
CHANGED
|
@@ -58,10 +58,10 @@ const utilities = require("./utilities");
|
|
|
58
58
|
* ## Getting Started
|
|
59
59
|
*
|
|
60
60
|
* The following end-to-end examples might help to get started with `confluentcloud.ClusterLink` resource:
|
|
61
|
-
* *
|
|
62
|
-
* *
|
|
63
|
-
* *
|
|
64
|
-
* *
|
|
61
|
+
* * destination-initiated-cluster-link-rbac: An example of setting up a _destination_ initiated cluster link with a mirror topic
|
|
62
|
+
* * source-initiated-cluster-link-rbac: An example of setting up a _source_ initiated cluster link with a mirror topic
|
|
63
|
+
* * regular-bidirectional-cluster-link-rbac: An example of setting up a bidirectional cluster link with 2 mirror topics
|
|
64
|
+
* * advanced-bidirectional-cluster-link-rbac: An example of setting up a bidirectional cluster link with 2 mirror topics ([advanced option](https://docs.confluent.io/cloud/current/multi-cloud/cluster-linking/cluster-links-cc.html#create-a-cluster-link-in-bidirectional-mode))
|
|
65
65
|
*
|
|
66
66
|
* See [Cluster Linking on Confluent Cloud](https://docs.confluent.io/cloud/current/multi-cloud/cluster-linking/index.html) to learn more about Cluster Linking on Confluent Cloud.
|
|
67
67
|
*
|
package/connector.d.ts
CHANGED
|
@@ -287,20 +287,20 @@ import * as outputs from "./types/output";
|
|
|
287
287
|
* ## Getting Started
|
|
288
288
|
*
|
|
289
289
|
* The following end-to-end examples might help to get started with `confluentcloud.Connector` resource:
|
|
290
|
-
* *
|
|
291
|
-
* *
|
|
292
|
-
* *
|
|
293
|
-
* *
|
|
294
|
-
* *
|
|
295
|
-
* *
|
|
296
|
-
* *
|
|
297
|
-
* *
|
|
298
|
-
* *
|
|
299
|
-
* *
|
|
300
|
-
* *
|
|
301
|
-
* *
|
|
302
|
-
* *
|
|
303
|
-
* *
|
|
290
|
+
* * s3-sink-connector
|
|
291
|
+
* * s3-sink-connector-assume-role
|
|
292
|
+
* * snowflake-sink-connector
|
|
293
|
+
* * managed-datagen-source-connector
|
|
294
|
+
* * elasticsearch-sink-connector
|
|
295
|
+
* * dynamo-db-sink-connector
|
|
296
|
+
* * mongo-db-source-connector
|
|
297
|
+
* * mongo-db-sink-connector
|
|
298
|
+
* * sql-server-cdc-debezium-source-connector
|
|
299
|
+
* * postgre-sql-cdc-debezium-source-connector
|
|
300
|
+
* * custom-datagen-source-connector
|
|
301
|
+
* * manage-offsets-github-source-connector
|
|
302
|
+
* * manage-offsets-mongo-db-source-connector
|
|
303
|
+
* * manage-offsets-mysql-sink-connector
|
|
304
304
|
*
|
|
305
305
|
* > **Note:** Certain connectors require additional ACL entries. See [Additional ACL entries](https://docs.confluent.io/cloud/current/connectors/service-account.html#additional-acl-entries) for more details.
|
|
306
306
|
*
|
package/connector.js
CHANGED
|
@@ -291,20 +291,20 @@ const utilities = require("./utilities");
|
|
|
291
291
|
* ## Getting Started
|
|
292
292
|
*
|
|
293
293
|
* The following end-to-end examples might help to get started with `confluentcloud.Connector` resource:
|
|
294
|
-
* *
|
|
295
|
-
* *
|
|
296
|
-
* *
|
|
297
|
-
* *
|
|
298
|
-
* *
|
|
299
|
-
* *
|
|
300
|
-
* *
|
|
301
|
-
* *
|
|
302
|
-
* *
|
|
303
|
-
* *
|
|
304
|
-
* *
|
|
305
|
-
* *
|
|
306
|
-
* *
|
|
307
|
-
* *
|
|
294
|
+
* * s3-sink-connector
|
|
295
|
+
* * s3-sink-connector-assume-role
|
|
296
|
+
* * snowflake-sink-connector
|
|
297
|
+
* * managed-datagen-source-connector
|
|
298
|
+
* * elasticsearch-sink-connector
|
|
299
|
+
* * dynamo-db-sink-connector
|
|
300
|
+
* * mongo-db-source-connector
|
|
301
|
+
* * mongo-db-sink-connector
|
|
302
|
+
* * sql-server-cdc-debezium-source-connector
|
|
303
|
+
* * postgre-sql-cdc-debezium-source-connector
|
|
304
|
+
* * custom-datagen-source-connector
|
|
305
|
+
* * manage-offsets-github-source-connector
|
|
306
|
+
* * manage-offsets-mongo-db-source-connector
|
|
307
|
+
* * manage-offsets-mysql-sink-connector
|
|
308
308
|
*
|
|
309
309
|
* > **Note:** Certain connectors require additional ACL entries. See [Additional ACL entries](https://docs.confluent.io/cloud/current/connectors/service-account.html#additional-acl-entries) for more details.
|
|
310
310
|
*
|
package/environment.d.ts
CHANGED
|
@@ -19,27 +19,27 @@ import * as outputs from "./types/output";
|
|
|
19
19
|
* ## Getting Started
|
|
20
20
|
*
|
|
21
21
|
* The following end-to-end examples might help to get started with `confluentcloud.Environment` resource:
|
|
22
|
-
* *
|
|
23
|
-
* *
|
|
24
|
-
* *
|
|
25
|
-
* *
|
|
26
|
-
* *
|
|
27
|
-
* *
|
|
28
|
-
* *
|
|
29
|
-
* *
|
|
30
|
-
* *
|
|
31
|
-
* *
|
|
32
|
-
* *
|
|
33
|
-
* *
|
|
34
|
-
* *
|
|
35
|
-
* *
|
|
36
|
-
* *
|
|
37
|
-
* *
|
|
38
|
-
* *
|
|
39
|
-
* *
|
|
40
|
-
* *
|
|
41
|
-
* *
|
|
42
|
-
* *
|
|
22
|
+
* * basic-kafka-acls: _Basic_ Kafka cluster with authorization using ACLs
|
|
23
|
+
* * basic-kafka-acls-with-alias: _Basic_ Kafka cluster with authorization using ACLs
|
|
24
|
+
* * standard-kafka-acls: _Standard_ Kafka cluster with authorization using ACLs
|
|
25
|
+
* * standard-kafka-rbac: _Standard_ Kafka cluster with authorization using RBAC
|
|
26
|
+
* * dedicated-public-kafka-acls: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using ACLs
|
|
27
|
+
* * dedicated-public-kafka-rbac: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using RBAC
|
|
28
|
+
* * dedicated-privatelink-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
29
|
+
* * dedicated-privatelink-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using RBAC
|
|
30
|
+
* * dedicated-privatelink-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using RBAC
|
|
31
|
+
* * dedicated-privatelink-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
32
|
+
* * dedicated-private-service-connect-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using ACLs
|
|
33
|
+
* * dedicated-private-service-connect-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using RBAC
|
|
34
|
+
* * dedicated-vnet-peering-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using ACLs
|
|
35
|
+
* * dedicated-vnet-peering-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using RBAC
|
|
36
|
+
* * dedicated-vpc-peering-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using ACLs
|
|
37
|
+
* * dedicated-vpc-peering-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using RBAC
|
|
38
|
+
* * dedicated-vpc-peering-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using ACLs
|
|
39
|
+
* * dedicated-vpc-peering-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using RBAC
|
|
40
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using ACLs
|
|
41
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using RBAC
|
|
42
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
43
43
|
*
|
|
44
44
|
* ## Import
|
|
45
45
|
*
|
package/environment.js
CHANGED
|
@@ -23,27 +23,27 @@ const utilities = require("./utilities");
|
|
|
23
23
|
* ## Getting Started
|
|
24
24
|
*
|
|
25
25
|
* The following end-to-end examples might help to get started with `confluentcloud.Environment` resource:
|
|
26
|
-
* *
|
|
27
|
-
* *
|
|
28
|
-
* *
|
|
29
|
-
* *
|
|
30
|
-
* *
|
|
31
|
-
* *
|
|
32
|
-
* *
|
|
33
|
-
* *
|
|
34
|
-
* *
|
|
35
|
-
* *
|
|
36
|
-
* *
|
|
37
|
-
* *
|
|
38
|
-
* *
|
|
39
|
-
* *
|
|
40
|
-
* *
|
|
41
|
-
* *
|
|
42
|
-
* *
|
|
43
|
-
* *
|
|
44
|
-
* *
|
|
45
|
-
* *
|
|
46
|
-
* *
|
|
26
|
+
* * basic-kafka-acls: _Basic_ Kafka cluster with authorization using ACLs
|
|
27
|
+
* * basic-kafka-acls-with-alias: _Basic_ Kafka cluster with authorization using ACLs
|
|
28
|
+
* * standard-kafka-acls: _Standard_ Kafka cluster with authorization using ACLs
|
|
29
|
+
* * standard-kafka-rbac: _Standard_ Kafka cluster with authorization using RBAC
|
|
30
|
+
* * dedicated-public-kafka-acls: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using ACLs
|
|
31
|
+
* * dedicated-public-kafka-rbac: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using RBAC
|
|
32
|
+
* * dedicated-privatelink-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
33
|
+
* * dedicated-privatelink-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using RBAC
|
|
34
|
+
* * dedicated-privatelink-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using RBAC
|
|
35
|
+
* * dedicated-privatelink-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
36
|
+
* * dedicated-private-service-connect-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using ACLs
|
|
37
|
+
* * dedicated-private-service-connect-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using RBAC
|
|
38
|
+
* * dedicated-vnet-peering-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using ACLs
|
|
39
|
+
* * dedicated-vnet-peering-azure-kafka-rbac: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using RBAC
|
|
40
|
+
* * dedicated-vpc-peering-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using ACLs
|
|
41
|
+
* * dedicated-vpc-peering-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using RBAC
|
|
42
|
+
* * dedicated-vpc-peering-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using ACLs
|
|
43
|
+
* * dedicated-vpc-peering-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using RBAC
|
|
44
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using ACLs
|
|
45
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using RBAC
|
|
46
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
47
47
|
*
|
|
48
48
|
* ## Import
|
|
49
49
|
*
|
|
@@ -24,8 +24,8 @@ import * as outputs from "./types/output";
|
|
|
24
24
|
* ## Getting Started
|
|
25
25
|
*
|
|
26
26
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachment` data source:
|
|
27
|
-
* *
|
|
28
|
-
* *
|
|
27
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
28
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
29
29
|
*/
|
|
30
30
|
export declare function getPrivateLinkAttachment(args: GetPrivateLinkAttachmentArgs, opts?: pulumi.InvokeOptions): Promise<GetPrivateLinkAttachmentResult>;
|
|
31
31
|
/**
|
|
@@ -101,8 +101,8 @@ export interface GetPrivateLinkAttachmentResult {
|
|
|
101
101
|
* ## Getting Started
|
|
102
102
|
*
|
|
103
103
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachment` data source:
|
|
104
|
-
* *
|
|
105
|
-
* *
|
|
104
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
105
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
106
106
|
*/
|
|
107
107
|
export declare function getPrivateLinkAttachmentOutput(args: GetPrivateLinkAttachmentOutputArgs, opts?: pulumi.InvokeOutputOptions): pulumi.Output<GetPrivateLinkAttachmentResult>;
|
|
108
108
|
/**
|
|
@@ -28,8 +28,8 @@ const utilities = require("./utilities");
|
|
|
28
28
|
* ## Getting Started
|
|
29
29
|
*
|
|
30
30
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachment` data source:
|
|
31
|
-
* *
|
|
32
|
-
* *
|
|
31
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
32
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
33
33
|
*/
|
|
34
34
|
function getPrivateLinkAttachment(args, opts) {
|
|
35
35
|
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
|
|
@@ -62,8 +62,8 @@ exports.getPrivateLinkAttachment = getPrivateLinkAttachment;
|
|
|
62
62
|
* ## Getting Started
|
|
63
63
|
*
|
|
64
64
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachment` data source:
|
|
65
|
-
* *
|
|
66
|
-
* *
|
|
65
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
66
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
67
67
|
*/
|
|
68
68
|
function getPrivateLinkAttachmentOutput(args, opts) {
|
|
69
69
|
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
|
|
@@ -24,8 +24,8 @@ import * as outputs from "./types/output";
|
|
|
24
24
|
* ## Getting Started
|
|
25
25
|
*
|
|
26
26
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachmentConnection` data source:
|
|
27
|
-
* *
|
|
28
|
-
* *
|
|
27
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
28
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
29
29
|
*/
|
|
30
30
|
export declare function getPrivateLinkAttachmentConnection(args: GetPrivateLinkAttachmentConnectionArgs, opts?: pulumi.InvokeOptions): Promise<GetPrivateLinkAttachmentConnectionResult>;
|
|
31
31
|
/**
|
|
@@ -95,8 +95,8 @@ export interface GetPrivateLinkAttachmentConnectionResult {
|
|
|
95
95
|
* ## Getting Started
|
|
96
96
|
*
|
|
97
97
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachmentConnection` data source:
|
|
98
|
-
* *
|
|
99
|
-
* *
|
|
98
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
99
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
100
100
|
*/
|
|
101
101
|
export declare function getPrivateLinkAttachmentConnectionOutput(args: GetPrivateLinkAttachmentConnectionOutputArgs, opts?: pulumi.InvokeOutputOptions): pulumi.Output<GetPrivateLinkAttachmentConnectionResult>;
|
|
102
102
|
/**
|
|
@@ -28,8 +28,8 @@ const utilities = require("./utilities");
|
|
|
28
28
|
* ## Getting Started
|
|
29
29
|
*
|
|
30
30
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachmentConnection` data source:
|
|
31
|
-
* *
|
|
32
|
-
* *
|
|
31
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
32
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
33
33
|
*/
|
|
34
34
|
function getPrivateLinkAttachmentConnection(args, opts) {
|
|
35
35
|
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
|
|
@@ -62,8 +62,8 @@ exports.getPrivateLinkAttachmentConnection = getPrivateLinkAttachmentConnection;
|
|
|
62
62
|
* ## Getting Started
|
|
63
63
|
*
|
|
64
64
|
* The following end-to-end examples might help to get started with `confluentcloud.PrivateLinkAttachmentConnection` data source:
|
|
65
|
-
* *
|
|
66
|
-
* *
|
|
65
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
66
|
+
* * enterprise-privatelinkattachment-azure-kafka-acls: _Enterprise_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
67
67
|
*/
|
|
68
68
|
function getPrivateLinkAttachmentConnectionOutput(args, opts) {
|
|
69
69
|
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
|
|
@@ -35,7 +35,7 @@ import * as outputs from "./types/output";
|
|
|
35
35
|
* ## Getting Started
|
|
36
36
|
*
|
|
37
37
|
* The following end-to-end examples might help to get started with `confluentcloud.ProviderIntegration` data source:
|
|
38
|
-
* *
|
|
38
|
+
* * s3-sink-connector-assume-role: Amazon S3 Sink Connector with IAM role-based authorization using a Provider Integration
|
|
39
39
|
*/
|
|
40
40
|
export declare function getProviderIntegration(args: GetProviderIntegrationArgs, opts?: pulumi.InvokeOptions): Promise<GetProviderIntegrationResult>;
|
|
41
41
|
/**
|
|
@@ -114,7 +114,7 @@ export interface GetProviderIntegrationResult {
|
|
|
114
114
|
* ## Getting Started
|
|
115
115
|
*
|
|
116
116
|
* The following end-to-end examples might help to get started with `confluentcloud.ProviderIntegration` data source:
|
|
117
|
-
* *
|
|
117
|
+
* * s3-sink-connector-assume-role: Amazon S3 Sink Connector with IAM role-based authorization using a Provider Integration
|
|
118
118
|
*/
|
|
119
119
|
export declare function getProviderIntegrationOutput(args: GetProviderIntegrationOutputArgs, opts?: pulumi.InvokeOutputOptions): pulumi.Output<GetProviderIntegrationResult>;
|
|
120
120
|
/**
|
|
@@ -39,7 +39,7 @@ const utilities = require("./utilities");
|
|
|
39
39
|
* ## Getting Started
|
|
40
40
|
*
|
|
41
41
|
* The following end-to-end examples might help to get started with `confluentcloud.ProviderIntegration` data source:
|
|
42
|
-
* *
|
|
42
|
+
* * s3-sink-connector-assume-role: Amazon S3 Sink Connector with IAM role-based authorization using a Provider Integration
|
|
43
43
|
*/
|
|
44
44
|
function getProviderIntegration(args, opts) {
|
|
45
45
|
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
|
|
@@ -84,7 +84,7 @@ exports.getProviderIntegration = getProviderIntegration;
|
|
|
84
84
|
* ## Getting Started
|
|
85
85
|
*
|
|
86
86
|
* The following end-to-end examples might help to get started with `confluentcloud.ProviderIntegration` data source:
|
|
87
|
-
* *
|
|
87
|
+
* * s3-sink-connector-assume-role: Amazon S3 Sink Connector with IAM role-based authorization using a Provider Integration
|
|
88
88
|
*/
|
|
89
89
|
function getProviderIntegrationOutput(args, opts) {
|
|
90
90
|
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
|
package/kafkaAcl.d.ts
CHANGED
|
@@ -53,20 +53,20 @@ import * as outputs from "./types/output";
|
|
|
53
53
|
* ## Getting Started
|
|
54
54
|
*
|
|
55
55
|
* The following end-to-end examples might help to get started with `confluentcloud.KafkaAcl` resource:
|
|
56
|
-
* *
|
|
57
|
-
* *
|
|
58
|
-
* *
|
|
59
|
-
* *
|
|
60
|
-
* *
|
|
61
|
-
* *
|
|
62
|
-
* *
|
|
63
|
-
* *
|
|
64
|
-
* *
|
|
65
|
-
* *
|
|
66
|
-
* *
|
|
67
|
-
* *
|
|
68
|
-
* *
|
|
69
|
-
* *
|
|
56
|
+
* * basic-kafka-acls: _Basic_ Kafka cluster with authorization using ACLs
|
|
57
|
+
* * basic-kafka-acls-with-alias: _Basic_ Kafka cluster with authorization using ACLs
|
|
58
|
+
* * standard-kafka-acls: _Standard_ Kafka cluster with authorization using ACLs
|
|
59
|
+
* * dedicated-public-kafka-acls: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using ACLs
|
|
60
|
+
* * dedicated-privatelink-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
61
|
+
* * dedicated-privatelink-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
62
|
+
* * dedicated-private-service-connect-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using ACLs
|
|
63
|
+
* * dedicated-private-service-connect-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using RBAC
|
|
64
|
+
* * dedicated-vnet-peering-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using ACLs
|
|
65
|
+
* * dedicated-vpc-peering-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using ACLs
|
|
66
|
+
* * dedicated-vpc-peering-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using ACLs
|
|
67
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using ACLs
|
|
68
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using RBAC
|
|
69
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
70
70
|
*
|
|
71
71
|
* ## Other Example Usages
|
|
72
72
|
*
|
package/kafkaAcl.js
CHANGED
|
@@ -57,20 +57,20 @@ const utilities = require("./utilities");
|
|
|
57
57
|
* ## Getting Started
|
|
58
58
|
*
|
|
59
59
|
* The following end-to-end examples might help to get started with `confluentcloud.KafkaAcl` resource:
|
|
60
|
-
* *
|
|
61
|
-
* *
|
|
62
|
-
* *
|
|
63
|
-
* *
|
|
64
|
-
* *
|
|
65
|
-
* *
|
|
66
|
-
* *
|
|
67
|
-
* *
|
|
68
|
-
* *
|
|
69
|
-
* *
|
|
70
|
-
* *
|
|
71
|
-
* *
|
|
72
|
-
* *
|
|
73
|
-
* *
|
|
60
|
+
* * basic-kafka-acls: _Basic_ Kafka cluster with authorization using ACLs
|
|
61
|
+
* * basic-kafka-acls-with-alias: _Basic_ Kafka cluster with authorization using ACLs
|
|
62
|
+
* * standard-kafka-acls: _Standard_ Kafka cluster with authorization using ACLs
|
|
63
|
+
* * dedicated-public-kafka-acls: _Dedicated_ Kafka cluster that is accessible over the public internet with authorization using ACLs
|
|
64
|
+
* * dedicated-privatelink-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
65
|
+
* * dedicated-privatelink-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via PrivateLink connections with authorization using ACLs
|
|
66
|
+
* * dedicated-private-service-connect-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using ACLs
|
|
67
|
+
* * dedicated-private-service-connect-gcp-kafka-rbac: _Dedicated_ Kafka cluster on GCP that is accessible via Private Service Connect connections with authorization using RBAC
|
|
68
|
+
* * dedicated-vnet-peering-azure-kafka-acls: _Dedicated_ Kafka cluster on Azure that is accessible via VPC Peering connections with authorization using ACLs
|
|
69
|
+
* * dedicated-vpc-peering-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via VPC Peering connections with authorization using ACLs
|
|
70
|
+
* * dedicated-vpc-peering-gcp-kafka-acls: _Dedicated_ Kafka cluster on GCP that is accessible via VPC Peering connections with authorization using ACLs
|
|
71
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-acls: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using ACLs
|
|
72
|
+
* * dedicated-transit-gateway-attachment-aws-kafka-rbac: _Dedicated_ Kafka cluster on AWS that is accessible via Transit Gateway Endpoint with authorization using RBAC
|
|
73
|
+
* * enterprise-privatelinkattachment-aws-kafka-acls: _Enterprise_ Kafka cluster on AWS that is accessible via PrivateLink connections with authorization using ACLs
|
|
74
74
|
*
|
|
75
75
|
* ## Other Example Usages
|
|
76
76
|
*
|