Closed JustinLex closed 1 month ago
Hi @JustinLex
Thanks for reporting this. I'll add an option in the preferences to disable those. In your workflow, iIs there still some value in less intrusive indications that the editor was changed (ex. * in the editor title, push icon gets highlighted) or can we drop any kind of modification-notification alltogether?
ps. Off the top of your head, is there any Is there anything that would help GitOps workflows and that is missing currently? I'd love to get your thoughts it you have any.
Hi @JustinLex
Am I right in thinking that you dont want any automatic sync with the cluster to happen? You only want to push & pull when you hit the toolbar buttons. Correct?
@JustinLex: I now offer a setting where you can prevent the editor from syncronizing with the cluster:
Sync is enabled by default. You can disable it and it'll survive a restart of the IDE.
If sync is disabled you're not bothered to push your editor when it's modified (when compared to the cluster resource). Notifications of a resource that was deleted on the cluster are not displayed either.
You're still told of the result of pushing via the toolbar ("Resource was updated/created") and errors are notified, too, of course.
Hope that this is matching your expectations 😃
The PushNotification is not useful for GitOps workflows, and it is distracting to the user. There should be an option to disable the PushNotification. (i.e. the "Push to create Deployment 'foobar'?" notification)