New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serializing the test cases for connection resource #10491
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @melinath, 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. |
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
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: Click here to see the affected service packages
|
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
/gcbrun |
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
proxy_destination_config { | ||
key = "proxy_destination_config" | ||
destination { | ||
host = "https://proxy.zendesk.com" | ||
port = 80 | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
proxy_destination_config { | |
key = "proxy_destination_config" | |
destination { | |
host = "https://proxy.zendesk.com" | |
port = 80 | |
} | |
} |
This is causing the error: Blocks of type "proxy_destination_config" are not expected here. I don't see this field documented for this resource: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/integration_connectors_connection
dead_letter_config{ | ||
topic = "test-topic" | ||
project_id = "test-project-id" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dead_letter_config{ | |
topic = "test-topic" | |
project_id = "test-project-id" | |
} |
This is causing the error: Blocks of type "dead_letter_config" are not expected here.
I don't see this field documented for this resource: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/integration_connectors_connection
.../terraform/services/integrationconnectors/resource_integration_connectors_connection_test.go
Show resolved
Hide resolved
.../terraform/services/integrationconnectors/resource_integration_connectors_connection_test.go
Show resolved
Hide resolved
.../terraform/services/integrationconnectors/resource_integration_connectors_connection_test.go
Show resolved
Hide resolved
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
5d6df5c
to
10fdd72
Compare
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.
Errors
|
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.
|
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
1 similar comment
Tests analyticsTotal tests: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
|
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
|
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: Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccIntegrationConnectorsConnection |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking as changes requested to track the t.Parallel()
change.
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: Click here to see the affected service packages
|
PTAL at convenience |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - the serialized tests are copies of the example tests plus a few small corrections to get them passing.
Would it make sense to backport the fixes to the examples we show in docs? (In a separate PR - this one is good to go!)
So the fixes are rather on our API layer than here, so there is actually nothing to backfill and its already inline |
There were a few changes you ended up making to the tests after serializing them, like adding explicit service accounts - I'm wondering if you might want to add those changes to the documented usage of the resource? |
Serializing the test cases for connection resource
Fixed hashicorp/terraform-provider-google#16720
Release Note Template for Downstream PRs (will be copied)