You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add eventarc trigger missing field event_data_content_type (#8235) (#6032)
* upgrade dcl version to v1.43.0
* add overrides samples for trigger event_data_content_type field
* Fix typo
* Upgrade dcl version to v1.47.0
* Upgrade dcl version to v1.48.0 to fix issues in previous version.
---------
Signed-off-by: Modular Magician <[email protected]>
Co-authored-by: Riley <[email protected]>
Description: "Immutable. Relative name of the cloud resource that contains the data that is being managed within a lake. For example: `projects/{project_number}/buckets/{bucket_id}` `projects/{project_number}/datasets/{dataset_id}`",
288
287
},
288
+
289
+
"read_access_mode": {
290
+
Type: schema.TypeString,
291
+
Computed: true,
292
+
Optional: true,
293
+
Description: "Optional. Determines how read permissions are handled for each asset and their associated tables. Only available to storage buckets assets. Possible values: DIRECT, MANAGED",
Description: "Optional. The name of the channel associated with the trigger in `projects/{project}/locations/{location}/channels/{channel}` format. You must provide a channel to receive events from Eventarc SaaS partners.",
91
91
},
92
92
93
+
"event_data_content_type": {
94
+
Type: schema.TypeString,
95
+
Optional: true,
96
+
Description: "Optional. EventDataContentType specifies the type of payload in MIME format that is expected from the CloudEvent data field. This is set to `application/json` if the value is not defined.",
97
+
},
98
+
93
99
"labels": {
94
100
Type: schema.TypeMap,
95
101
Optional: true,
@@ -323,15 +329,16 @@ func resourceEventarcTriggerCreate(d *schema.ResourceData, meta interface{}) err
Copy file name to clipboardExpand all lines: website/docs/r/clouddeploy_delivery_pipeline.html.markdown
+64Lines changed: 64 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,6 +277,14 @@ The `phase_configs` block supports:
277
277
(Required)
278
278
Required. The ID to assign to the `Rollout` phase. This value must consist of lower-case letters, numbers, and hyphens, start with a letter and end with a letter or a number, and have a max length of 63 characters. In other words, it must match the following regex: `^[a-z]([a-z0-9-]{0,61}[a-z0-9])?$`.
279
279
280
+
*`postdeploy` -
281
+
(Optional)
282
+
(Beta only) Optional. Configuration for the postdeploy job of this phase. If this is not configured, postdeploy job will not be present for this phase.
283
+
284
+
*`predeploy` -
285
+
(Optional)
286
+
(Beta only) Optional. Configuration for the predeploy job of this phase. If this is not configured, predeploy job will not be present for this phase.
287
+
280
288
*`profiles` -
281
289
(Optional)
282
290
Skaffold profiles to use when rendering the manifest for this phase. These are in addition to the profiles list specified in the `DeliveryPipeline` stage.
@@ -377,16 +385,48 @@ The `canary_deployment` block supports:
377
385
(Required)
378
386
Required. The percentage based deployments that will occur as a part of a `Rollout`. List is expected in ascending order and each integer n is 0 <= n < 100.
379
387
388
+
*`postdeploy` -
389
+
(Optional)
390
+
(Beta only) Optional. Configuration for the postdeploy job of the last phase. If this is not configured, postdeploy job will not be present.
391
+
392
+
*`predeploy` -
393
+
(Optional)
394
+
(Beta only) Optional. Configuration for the predeploy job of the first phase. If this is not configured, predeploy job will not be present.
395
+
380
396
*`verify` -
381
397
(Optional)
382
398
Whether to run verify tests after each percentage deployment.
383
399
400
+
The `postdeploy` block supports:
401
+
402
+
*`actions` -
403
+
(Optional)
404
+
Optional. A sequence of skaffold custom actions to invoke during execution of the postdeploy job.
405
+
406
+
The `predeploy` block supports:
407
+
408
+
*`actions` -
409
+
(Optional)
410
+
Optional. A sequence of skaffold custom actions to invoke during execution of the predeploy job.
411
+
384
412
The `custom_canary_deployment` block supports:
385
413
386
414
*`phase_configs` -
387
415
(Required)
388
416
Required. Configuration for each phase in the canary deployment in the order executed.
389
417
418
+
The `postdeploy` block supports:
419
+
420
+
*`actions` -
421
+
(Optional)
422
+
Optional. A sequence of skaffold custom actions to invoke during execution of the postdeploy job.
423
+
424
+
The `predeploy` block supports:
425
+
426
+
*`actions` -
427
+
(Optional)
428
+
Optional. A sequence of skaffold custom actions to invoke during execution of the predeploy job.
429
+
390
430
The `runtime_config` block supports:
391
431
392
432
*`cloud_run` -
@@ -423,6 +463,10 @@ The `gateway_service_mesh` block supports:
423
463
(Required)
424
464
Required. Name of the Gateway API HTTPRoute.
425
465
466
+
*`route_update_wait_time` -
467
+
(Optional)
468
+
Optional. The time to wait for route updates to propagate. The maximum configurable time is 3 hours, in seconds format. If unspecified, there is no wait time.
469
+
426
470
*`service` -
427
471
(Required)
428
472
Required. Name of the Kubernetes Service.
@@ -443,10 +487,30 @@ The `service_networking` block supports:
443
487
444
488
The `standard` block supports:
445
489
490
+
*`postdeploy` -
491
+
(Optional)
492
+
(Beta only) Optional. Configuration for the postdeploy job. If this is not configured, postdeploy job will not be present.
493
+
494
+
*`predeploy` -
495
+
(Optional)
496
+
(Beta only) Optional. Configuration for the predeploy job. If this is not configured, predeploy job will not be present.
497
+
446
498
*`verify` -
447
499
(Optional)
448
500
Whether to verify a deployment.
449
501
502
+
The `postdeploy` block supports:
503
+
504
+
*`actions` -
505
+
(Optional)
506
+
Optional. A sequence of skaffold custom actions to invoke during execution of the postdeploy job.
507
+
508
+
The `predeploy` block supports:
509
+
510
+
*`actions` -
511
+
(Optional)
512
+
Optional. A sequence of skaffold custom actions to invoke during execution of the predeploy job.
513
+
450
514
## Attributes Reference
451
515
452
516
In addition to the arguments listed above, the following computed attributes are exported:
Copy file name to clipboardExpand all lines: website/docs/r/dataplex_asset.html.markdown
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,6 +148,10 @@ The `resource_spec` block supports:
148
148
(Optional)
149
149
Immutable. Relative name of the cloud resource that contains the data that is being managed within a lake. For example: `projects/{project_number}/buckets/{bucket_id}``projects/{project_number}/datasets/{dataset_id}`
150
150
151
+
*`read_access_mode` -
152
+
(Optional)
153
+
Optional. Determines how read permissions are handled for each asset and their associated tables. Only available to storage buckets assets. Possible values: DIRECT, MANAGED
154
+
151
155
*`type` -
152
156
(Required)
153
157
Required. Immutable. Type of resource. Possible values: STORAGE_BUCKET, BIGQUERY_DATASET
Copy file name to clipboardExpand all lines: website/docs/r/eventarc_trigger.html.markdown
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,6 +135,10 @@ The `matching_criteria` block supports:
135
135
(Optional)
136
136
Optional. The name of the channel associated with the trigger in `projects/{project}/locations/{location}/channels/{channel}` format. You must provide a channel to receive events from Eventarc SaaS partners.
137
137
138
+
*`event_data_content_type` -
139
+
(Optional)
140
+
Optional. EventDataContentType specifies the type of payload in MIME format that is expected from the CloudEvent data field. This is set to `application/json` if the value is not defined.
141
+
138
142
*`labels` -
139
143
(Optional)
140
144
Optional. User labels attached to the triggers that can be used to group resources.
0 commit comments