Conversation
…or dataplex_datascan_execution_identity_service_account
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 83 Click here to see the affected service packages
🟢 All tests passed! View the build log |
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @roaks3, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
c956bb4
this pr is to fix hashicorp/terraform-provider-google#26716
The tests were failing/flaky because one time datascan triggers a datascan job run right after creation, and since examples scans have trivial setup so the job run could be quick, and therefore, when the pipeline performs import test, it will see the execution_status.0.latest_job_end_time being populated which leads to mismatch.
In this pr we also removed the used of redundant ignore_read_extra for dataplex_datascan_execution_identity_service_account as it uses an on_demand trigger which won't trigger a new scan job.