Public outbound ip

[prabhav2302]

This PR adds the enableOutboundPublicIp boolean field and outboundPublicIpAddresses (output only field) to the AlloyDB instance resource. Setting this field to true enables public outbound IP within the AlloyDB instance. PR addresses (b/353749975). It also adds testing which covers:

1. Creating an instance with the enableOutboundPublicIp set to true
2. Updating an instance with the enableOutboundPublicIp set to false
3. Updating an instance with the enableOutboundPublicIp set to true

Release Note Template for Downstream PRs (will be copied)

alloyDB: added `enableOutboundPublicIp` field to `google_alloydb_instance` resource

[github-actions]

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@hao-nan-li, 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.

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 68 insertions(+), 12 deletions(-))
google-beta provider: Diff ( 3 files changed, 68 insertions(+), 12 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 11 insertions(+))

[modular-magician]

Tests analytics

Total tests: 73
Passed tests: 68
Skipped tests: 4
Affected tests: 1

Click here to see the affected service packages

• alloydb

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccAlloydbInstance_networkConfig

Get to know how VCR tests work

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
google-beta provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 11 insertions(+))

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
google-beta provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 11 insertions(+))

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
google-beta provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 11 insertions(+))

[modular-magician]

Tests analytics

Total tests: 73
Passed tests: 68
Skipped tests: 4
Affected tests: 1

Click here to see the affected service packages

• alloydb

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccAlloydbInstance_networkConfig

Get to know how VCR tests work

[modular-magician]

Tests analytics

Total tests: 73
Passed tests: 68
Skipped tests: 4
Affected tests: 1

Click here to see the affected service packages

• alloydb

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccAlloydbInstance_networkConfig

Get to know how VCR tests work

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
google-beta provider: Diff ( 3 files changed, 68 insertions(+), 7 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 11 insertions(+))

[modular-magician]

Tests analytics

Total tests: 73
Passed tests: 68
Skipped tests: 4
Affected tests: 1

Click here to see the affected service packages

• alloydb

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccAlloydbInstance_networkConfig

Get to know how VCR tests work

[modular-magician]

Tests analytics

Total tests: 73
Passed tests: 68
Skipped tests: 4
Affected tests: 1

Click here to see the affected service packages

• alloydb

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccAlloydbInstance_networkConfig

Get to know how VCR tests work

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbInstance_networkConfig[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbInstance_networkConfig[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbInstance_networkConfig[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbInstance_networkConfig[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbInstance_networkConfig[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[hao-nan-li]

output:true fields is optional, but it's fine to have it here.