Add the note using Create method to create google_service_networking_connection to 5.0 guide

[zli82016]

Release Note Template for Downstream PRs (will be copied)

docs: added the note using Create method to create google_service_networking_connection to 5.0 guide

[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.

Terraform GA: Diff ( 1 file changed, 6 insertions(+))
Terraform Beta: Diff ( 1 file changed, 6 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.

Terraform GA: Diff ( 1 file changed, 6 insertions(+))
Terraform Beta: Diff ( 1 file changed, 6 insertions(+))

[modular-magician]

Tests analytics

Total tests: 3018
Passed tests 2720
Skipped tests: 297
Affected tests: 1

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

TestAccDataprocJobIamPolicy

Get to know how VCR tests work

[modular-magician]

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

Rerun these tests in REPLAYING mode to catch issues

$\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

[c2thorn]

Suggested change

Previously, Patch instead of Create is used to create the resource, because an error message is returned when creating multiple SQL instances after creating `google_service_networking_connection` with Create method. See more details in https://issuetracker.google.com/issues/131908322. Now the issue has been fixed. The initial workaround of using Patch is no longer needed. Create method is used to create the resource.

`google_service_networking_connection` now uses the Create endpoint instead of the Patch endpoint during the creation step. Previously, Patch was used as a workaround for an issue that has since been resolved.

• I don't think we need to include the issue tracker, it wasn't particularly helpful for me understanding the issue.
• When you say "The initial workaround of using Patch is no longer needed" are you telling users to do something, or is it already taken care of?
• Are there any other specific steps the user needs to take when upgrading?
• Also, can we be more specific about Patch and Create? Like "Patch endpoint" or something?

[zli82016]

Thanks for the suggestion.

• When you say "The initial workaround of using Patch is no longer needed" are you telling users to do something, or is it already taken care of?
  • It is already taken care by using Create endpoint
• Are there any other specific steps the user needs to take when upgrading?
  • The user does not need to take any other steps.

[c2thorn]

Thanks for the explanations!

[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.

Terraform GA: Diff ( 1 file changed, 6 insertions(+))
Terraform Beta: Diff ( 1 file changed, 6 insertions(+))