Added variable for activating nat and implementation in google_apigee… #2999
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
…_net_address resource
juliocc
approved these changes
Apr 2, 2025
juliocc
reviewed
Apr 2, 2025
auto-merge was automatically disabled
April 4, 2025 05:33
Head branch was pushed to by a user without write access
…/cloud-foundation-fabric into apigee-activate-nat-2940
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows you to set the activation status of an apigee NAT object. Previously it had to be manually activated by api calls or if it's imported and the status is different from the default (only option available at the moment) it will perpetually try to update this.
I applicable, I acknowledge that I have:
terraform fmton all modified filestools/tfdoc.pyNo breaking changes, defaults to false as-is currently the default.