Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enhance container management and UI with version info and fixes #464
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
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Enhance container management and UI with version info and fixes #464
Changes from all commits
69f8f72d139833b38afebe3cb7adFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is doing exactly what the ticket asked for but I don't fully agree with the logic. The real problem with the implicit restart is that if, for example, the admin changed the default container vars, that would queue a restart regardless of the change the user made (possibly even if they made no changes). In reality, the implicit restart is good if the user intentionally changes entrypoint/environment because otherwise they may be left to wonder why their changes didn't take effect. Really there's 2 problems here:
We can hook into this new solution to fix both of these, but we need one more layer on top. We keep this new "no restarts by default" logic to keep admin changes from bleeding into the container lifecycle behavior BUT if the user makes environment or entrypoint changes (or anything else requiring a restart) then some sort of noticable but unobtrusive UI affordance informs the user that this change requires a restart and the "restart" toggle is switched on. The user can still switch this off manually afterwards but another warning (under the toggle maybe) "this change requires a restart but a restart will not be performed".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.