-
Notifications
You must be signed in to change notification settings - Fork 642
fix!: remove deprecated workflows client #6790
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
Conversation
…client, from google-cloud-workflows-executions
|
Merge #6789 first |
|
This is a very unexpected breaking change And your advice to "Please use the ExecutionsClient instead" is nonsensical. ExecutionsClient handles executing workflows (run, cancel, list executions). It has nothing to do with creating or deploying workflow definitions. These are two completely different REST API services:
You removed the client for the first one and told us to use the client for the second one, which doesn't cover the same operations at all. Now there is no way for us to programatically create Workflows, we can only execute Workflows that have already been created. |
see #6789
This is a separate PR since this is a breaking change. We are removing the workflows client from both the v1beta and v1 surfaces. Please use the ExecutionsClient instead.