Cluster Applications: Allow for the user to retry an update on `update_errored`
Problem to solve
After an application fails update (update_errored) the user should be able to retry an update, currently this action is not available, see below:
The last few lines of the status_reason are:
...Skip local chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
+ helm upgrade prometheus stable/prometheus --reuse-values --tls --tls-ca-cert /data/helm/prometheus/config/ca.pem --tls-cert /data/helm/prometheus/config/cert.pem --tls-key /data/helm/prometheus/config/key.pem --version 9.5.2 --namespace gitlab-managed-apps -f /data/helm/prometheus/config/values.yaml
UPGRADE FAILED
Error: render error in "prometheus/templates/server-podsecuritypolicy.yaml": template: prometheus/templates/server-podsecuritypolicy.yaml:2:14: executing "prometheus/templates/server-podsecuritypolicy.yaml" at <.Values.podSecurityPolicy.enabled>: nil pointer evaluating interface {}.enabled
Error: UPGRADE FAILED: render error in "prometheus/templates/server-podsecuritypolicy.yaml": template: prometheus/templates/server-podsecuritypolicy.yaml:2:14: executing "prometheus/templates/server-podsecuritypolicy.yaml" at <.Values.podSecurityPolicy.enabled>: nil pointer evaluating interface {}.enabled
"
Intended users
Proposal
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Miguel Rincon
