-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Redis cluster Multi vpc support #12548
base: main
Are you sure you want to change the base?
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @NickElliot, 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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_redis_cluster" "primary" {
cluster_endpoints = # value needed
psc_service_attachments {
connection_type = # value needed
service_attachment = # value needed
}
}
Resource: resource "google_redis_cluster_user_created_connections" "primary" {
cluster_endpoints = # value needed
}
|
Tests analyticsTotal tests: 27 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 tests
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_redis_cluster" "primary" {
cluster_endpoints = # value needed
psc_service_attachments {
connection_type = # value needed
service_attachment = # value needed
}
}
Resource: resource "google_redis_cluster_user_created_connections" "primary" {
cluster_endpoints = # value needed
}
|
Tests analyticsTotal tests: 27 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 tests
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_redis_cluster" "primary" {
cluster_endpoints {
connections {
psc_auto_connection {
network = # value needed
project_id = # value needed
}
}
}
psc_service_attachments {
connection_type = # value needed
service_attachment = # value needed
}
}
Resource: resource "google_redis_cluster_user_created_connections" "primary" {
cluster_endpoints {
connections {
psc_connection {
project_id = # value needed
}
}
}
}
|
Tests analyticsTotal tests: 27 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 tests
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_redis_cluster" "primary" {
cluster_endpoints {
connections {
psc_auto_connection {
network = # value needed
project_id = # value needed
}
}
}
psc_service_attachments {
connection_type = # value needed
service_attachment = # value needed
}
}
Resource: resource "google_redis_cluster_user_created_connections" "primary" {
cluster_endpoints {
connections {
psc_connection {
project_id = # value needed
}
}
}
}
|
Tests analyticsTotal tests: 4373 Click here to see the affected service packages
Action takenFound 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🟢 Tests passed during RECORDING mode: 🔴 Tests failed when rerunning REPLAYING mode: Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
@NickElliot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
@@ -492,7 +492,7 @@ properties: | |||
For Private Service Connect forwarding rules that forward traffic to managed services, the target must be a service attachment. | |||
update_url: 'projects/{{project}}/regions/{{region}}/forwardingRules/{{name}}/setTarget' | |||
update_verb: 'POST' | |||
diff_suppress_func: 'tpgresource.CompareSelfLinkRelativePaths' | |||
diff_suppress_func: 'tpgresource.CompareSelfLinkRelativePathsWithProjectNumSuppress' |
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.
# google_compute_forwarding_rule.forwarding_rule1_network1 will be updated in-place
~ resource "google_compute_forwarding_rule" "forwarding_rule1_network1" {
id = "projects/ci-test-project-188019/regions/us-central1/forwardingRules/forwardingrule11"
name = "forwardingrule11"
~ target = "https://www.googleapis.com/compute/beta/projects/ma3f380586e1b5da2p-tp/regions/us-central1/serviceAttachments/gcp-memorystore-auto-3a9ed5c5-0e48-49-psc-sa" -> "https://www.googleapis.com/compute/v1/projects/91977256640/regions/us-central1/serviceAttachments/gcp-memorystore-auto-3a9ed5c5-0e48-49-psc-sa"
# (28 unchanged attributes hidden)
# (1 unchanged block hidden)
}
It looks like this diff suppress isn't working fully, are you getting different results locally?
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.
Fixed the issue. It should work now. But facing this new issue https://paste.googleplex.com/5853800871755776
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_redis_cluster" "primary" {
cluster_endpoints {
connections {
psc_auto_connection {
network = # value needed
project_id = # value needed
}
}
}
psc_service_attachments {
connection_type = # value needed
service_attachment = # value needed
}
}
Resource: resource "google_redis_cluster_user_created_connections" "primary" {
cluster_endpoints {
connections {
psc_connection {
project_id = # value needed
}
}
}
}
|
Tests analyticsTotal tests: 4382 Click here to see the affected service packages
Action takenFound 4 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🟢 Tests passed during RECORDING mode: 🔴 Tests failed when rerunning REPLAYING mode: Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. 🔴 Tests failed during RECORDING mode: 🔴 Several tests terminated during RECORDING mode. 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
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.
add output:true to the subfields of the new output field block, not sure about the test failure, will see if it repeats on a rerun
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_redis_cluster_user_created_connections" "primary" {
cluster_endpoints {
connections {
psc_connection {
address = # value needed
forwarding_rule = # value needed
network = # value needed
project_id = # value needed
psc_connection_id = # value needed
service_attachment = # value needed
}
}
}
name = # value needed
}
|
Tests analyticsTotal tests: 4383 Click here to see the affected service packages
Action takenFound 4 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🟢 Tests passed during RECORDING mode: 🔴 Tests failed when rerunning REPLAYING mode: Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
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: 4383 Click here to see the affected service packages
Action takenFound 6 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
It's the latter. ClusterEndpoints can have both user and auto created connections.
|
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: 0 Click here to see the affected service packages
🔴 Tests were added that are skipped in VCR:
View the build log |
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: 0 Click here to see the affected service packages
🔴 Tests were added that are skipped in VCR:
View the build log |
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: 29 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 tests
|
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: 29 Click here to see the affected service packages
🟢 All tests passed! View the build log |
@NickElliot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
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: 29 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 tests
|
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.
because the UserCreatedConnections has exclude_delete=true
and what the function does when it is supplied "0" means the google_redis_cluster_user_created_connections
resource is removed from plan entirely rather than processed as a change that needs to be applied
a custom delete will need to be added that applies the DELETE call as a patch command
userEndpointCount int | ||
} | ||
|
||
func createRedisClusterEndpoints(params *ClusterParams) string { |
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.
there is no case for when userEndpointCount=0, making it equivalent to removing these resources from state
…te endpoints when the resource is deleted
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: 29 Click here to see the affected service packages
Action takenFound 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
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.
pending cyclic dependency design decision
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.