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

fix(sensor-controller): Return err when a sensor spec is invalid. Fixes #1017 #1018

Merged
merged 2 commits into from
Jan 19, 2021

Conversation

whynowy
Copy link
Member

@whynowy whynowy commented Jan 13, 2021

Fixes #1017

Signed-off-by: Derek Wang whynowy@gmail.com

Checklist:

@whynowy whynowy requested review from alexec and VaibhavPage January 14, 2021 01:37
@whynowy whynowy merged commit f9d2cc0 into argoproj:master Jan 19, 2021
@whynowy whynowy deleted the duplicate-dep branch January 19, 2021 17:29
whynowy added a commit that referenced this pull request Jan 26, 2021
juliev0 pushed a commit to juliev0/argo-events that referenced this pull request Mar 29, 2022
@nielstenboom
Copy link

Would it be possible to undo this change? Because after this change new deployments to Kubernetes with Argo events objects fail silently if you made a mistake in the spec. Before this change the deployment would end up in a Crashloopbackoff causing alerts to go off and ArgoCD to show visually something is wrong, this is not the case any longer. I ran into this problem today.

I'd like to argue that generating a deployment when you made an error in the spec is safer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid sensor spec still generates deployments
3 participants