Skip to content
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

google_dataflow_job - when updating, wait for new job to start #6534

Conversation

modular-magician
Copy link
Collaborator

Release Note Template for Downstream PRs (will be copied)

dataflow: changed the update logic for `google_dataflow_job` to wait for the replacement job to start successfully before modifying the resource ID to point to the replacement job

Derived from GoogleCloudPlatform/magic-modules#3591

…corp#3591)

This patch modifies the update-by-replacement logic to wait for the new
job to start before updating the google_dataflow_job's resource ID to
point to the new job's ID. This ensures that the google_dataflow_job
resource continues to point to the original job if the update operation
were to fail.

Signed-off-by: Modular Magician <[email protected]>
@ghost ghost added the size/s label Jun 4, 2020
@modular-magician modular-magician merged commit 5b06674 into hashicorp:master Jun 4, 2020
@ghost
Copy link

ghost commented Jul 5, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Jul 5, 2020
@modular-magician modular-magician deleted the downstream-pr-3622c15b2d464c4deb0b7ac27677f3aa46b5cac3 branch November 17, 2024 00:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant