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

Remove startup_probe and liveness_probe fields from google_cloud_run_v2_job resource #13506

Closed
shuyama1 opened this issue Jan 17, 2023 · 3 comments

Comments

@shuyama1
Copy link
Collaborator

shuyama1 commented Jan 17, 2023

Cloud run job does not support probe currently and has no plan to support startup_probe and liveness_probe fields in the future. Recently, a validation is rolled out and starts to fail users potentially and our tests in nightly: https://ci-oss.hashicorp.engineering/buildConfiguration/GoogleCloudBeta_ProviderGoogleCloudBetaGoogleProject/367481?buildTab=tests&status=failed&name=TestAccCloudRunV2Job&pager.currentPage=1

startup_probe and liveness_probe need to be removed from google_cloud_run_v2_job in the next major release.

b/293328006

@yanweiguo
Copy link
Contributor

Please remove liveness_probe.tcp_socket as well since it's not supported.

@c2thorn
Copy link
Collaborator

c2thorn commented Sep 11, 2023

closed with GoogleCloudPlatform/magic-modules#8529

This will release with v5.0.0. Check #15582 for more details on the major release.

@c2thorn c2thorn closed this as completed Sep 11, 2023
@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants