Closed pietern closed 1 week ago
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:
Trigger: go/deco-tests-run/cli
Inputs:
93c569a5d3428d2ad0f1d5a1ff9002a72a4783e2
Checks will be approved automatically on success.
Test Details: go/deco-tests/11837584085
Beware: this bump does NOT include the proposed changes to the quality_monitor
resource.
The TF provider implementation was changed to use the plugin framework for this resource, and since then, it no longer includes whether a nested object is a single block (list with max 1 item) or multiple blocks (list with any number of items).
We use the former condition to inline a nested object as a pointer type. Without this condition, we must embed it as a slice type, and we can no longer convert between our representation and the TF representation.
I manually confirmed that we can continue to use the nester object as a pointer type. TF performs the conversion (I think) and interprets the nested object correctly as a list of size 1.
Changes
Notable changes:
restart_window
for pipelines.catalog
contains uppercase characters.See:
Tests
Integration tests pass.