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
Found internally - not necessarily blocking but very confusing experience
Earliest tried was 2022.3 build 349-hotfix.1272
No response
I updated the inline YAML on an existing Deploy Raw Kubernetes YAML step. The YAML appears to be invalid (the number should be surrounded by quotes).
When saving the process, no error message is presented, but the process is not saved. The Save button stays enabled.
apiVersion: v1 metadata: name: development --- kind: RoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: rbac-development namespace: development subjects: - kind: User name: 111195243876388272360 apiGroup: rbac.authorization.k8s.io roleRef: kind: ClusterRole name: edit apiGroup: rbac.authorization.k8s.io
The text was updated successfully, but these errors were encountered:
Release Note: Fixed an issue with Deploy Kubernetes Raw YAML step not showing any errors on attempting to save when provided with an invalid YAML
Sorry, something went wrong.
🎉 The fix for this issue has been released in:
mik-ky
No branches or pull requests
Team
Severity
Found internally - not necessarily blocking but very confusing experience
Version
Earliest tried was 2022.3 build 349-hotfix.1272
Latest Version
No response
What happened?
I updated the inline YAML on an existing Deploy Raw Kubernetes YAML step. The YAML appears to be invalid (the number should be surrounded by quotes).
When saving the process, no error message is presented, but the process is not saved. The Save button stays enabled.
Reproduction
Error and Stacktrace
No response
More Information
No response
Workaround
No response
The text was updated successfully, but these errors were encountered: