-
Notifications
You must be signed in to change notification settings - Fork 34
Successful output in case of errors in the applying process #278
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
Comments
I did more research and came to the conclusion that it's a problem between backends in different subscriptions. We use Azure, so we have to switch between subscriptions with the |
It looks like an error handling bug at the unit initialization stage. I don't think that the technical reason for the initialization error matters. I will check. |
I can send clearer code, as an example, to reproduce the error. In general, the error occurs when I use a Kubernetes or Helm Unit with a single cluster context that is only accessible from its corresponding Azure subscription. If I switch to another subscription, it gives this Unite processing error, which is correct. However, the problem is that the final output says that apply was successful, even though it is not. This misled me until I went through the cdev output in detail. |
No need. |
Uh oh!
There was an error while loading. Please reload this page.
Problem:
In the applying process, if there was an error, the final output doesn't let you know about it:
Cluster.dev Version:
cdev version v0.9.5
P.S.
To clarify, there was an error in the backend container name
The text was updated successfully, but these errors were encountered: