This repository has been archived by the owner on Jul 26, 2024. It is now read-only.
Add lb_backend_address_pool to remote #509
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@arnaudlh can you please take a look at this PR? Thanks in advance! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added lb_backend_address_pool to local.remote.tf to make possible to create a network_interface_backend_address_pool_association from another LZ.
Does this introduce a breaking change
Testing
Create a Load Balancer with backendpools and then in another LZ create a network_interface_backend_address_pool_association and refer with a lz_key to the backendpools.
Without this change it was not possible to refer from another LZ to the LB backendpool.