We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.status
I made a mistake here, and learnt something.
Once you introduce a status sub-resource, you can no longer patch the whole resource, for example:
kubectl patch wfts template-executor-jfmfn -p '{"status": {"nodes": {"template-executor-jfmfn": {"message": "ok"}}}}' --type merge workflowtaskset.argoproj.io/template-executor-jfmfn patched (no change)
See that there was "no change".
That means that changing to use workflowtaskset/status is a breaking change.
workflowtaskset/status
For users that are impacted by this, there is an espace hatch - do not install new manifests. This is a bad solution.
The text was updated successfully, but these errors were encountered:
This hasn't been released yet though, right? #7987
Should we try to cover this in tests and make sure we can always patch the resource?
Sorry, something went wrong.
It's not fixable. And I don't want to fix it. We could delay #7987 to v3.4.
fix!: Document how workflowtastset breaking change. Fixes argoproj#8013
6139c54
Signed-off-by: Alex Collins <alex_collins@intuit.com>
workflowtastset
fix!: Document workflowtaskset breaking change. Fixes #8013 (#8015)
workflowtaskset
c5c3b31
alexec
Successfully merging a pull request may close this issue.
I made a mistake here, and learnt something.
Once you introduce a status sub-resource, you can no longer patch the whole resource, for example:
kubectl patch wfts template-executor-jfmfn -p '{"status": {"nodes": {"template-executor-jfmfn": {"message": "ok"}}}}' --type merge workflowtaskset.argoproj.io/template-executor-jfmfn patched (no change)
See that there was "no change".
That means that changing to use
workflowtaskset/status
is a breaking change.For users that are impacted by this, there is an espace hatch - do not install new manifests. This is a bad solution.
The text was updated successfully, but these errors were encountered: