-
Notifications
You must be signed in to change notification settings - Fork 230
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
app: backend: Add flag for watching plugins changes #2939
base: main
Are you sure you want to change the base?
Conversation
ebff55f
to
1aee38b
Compare
Backend Code coverage changed from 65.0% to 65.2%. Change: .2% 😃. Coverage report
|
Backend Code coverage changed from 65.0% to 65.1%. Change: .1% 😃. Coverage report
|
1aee38b
to
7b99366
Compare
Backend Code coverage changed from 65.1% to 65.0%. Change: -.1% 😞. Coverage report
|
91ffcee
to
4441ebe
Compare
Backend Code coverage changed from 65.0% to 65.0%. Change: 0% 😃. Coverage report
|
A few small changes...
|
Dockerfile
Outdated
@@ -95,4 +95,4 @@ USER headlamp | |||
EXPOSE 4466 | |||
|
|||
ENV HEADLAMP_STATIC_PLUGINS_DIR=/headlamp/static-plugins | |||
ENTRYPOINT ["/headlamp/headlamp-server", "-html-static-dir", "/headlamp/frontend", "-plugins-dir", "/headlamp/plugins"] | |||
ENTRYPOINT ["/headlamp/headlamp-server", "-html-static-dir", "/headlamp/frontend", "-plugins-dir", "/headlamp/plugins", "-watch-plugins-changes", "false"] |
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.
Added this. @joaquimrocha please review?
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.
Hrmm… Adding this seems to stop the container tests from passing.
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.
Is there a good reason for keeping this here? If it's being problematic I suppose we could remove it
Backend Code coverage changed from 65.0% to 65.0%. Change: 0% 😃. Coverage report
|
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.
👍 thanks
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.
The container tests are failing now that I added the watch false option into the container and I’m not sure why yet.
(restarted them twice)
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.
Found a possible issue, as commented in line.
Also would it make sense to have it as false by default? It would break the behavior we currently have (where it's on unless -in-cluster), but I feel like the use cases for having it on by default are less than otherwise. I am fine if we don't make it false by default on the grounds of keeping the behavior we had.
4441ebe
to
aac4f48
Compare
Backend Code coverage changed from 65.0% to 65.3%. Change: .3% 😃. Coverage report
|
This change creates a CLI flag in the backend + desktop for watching changes to the plugins or their directory. Stops watching for plugin changes in the container image. Fixes: #2894 Signed-off-by: Evangelos Skopelitis <eskopelitis@microsoft.com> Signed-off-by: René Dudfield <renedudfield@microsoft.com>
aac4f48
to
deb2603
Compare
Backend Code coverage changed from 64.9% to 65.1%. Change: .2% 😃. Coverage report
|
This change creates a CLI flag in the backend + desktop for watching changes to the plugins or their directory.
Fixes: #2894
Testing
Backend
make backend
cd backend && ./headlamp-server -watch-plugins-changes false
Desktop
cd app && npm run build
cd dist/linux-unpacked && ./headlamp -watch-plugins-changes false
and ensure that the flag is passed in