Allow API_USER to have access to commands #136
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.
Without this line added, the API_USER account cannot do things like enable/disable the beeper
Summary of Changes
I added in a line to the entrypoint.sh that allows the API_USER to issue commands. This was the workaround fix I made on for my own uses. The sample uspd.users file mentions how
instcmds
works hereWhy is this change being made?
This is needed in order to have Home Assistant do commands such as enable/disable the beeper.
How was this tested? How can the reviewer verify your testing?
Without this change, I got an access denied message when trying to run commands. I replaced the original entrypoint.sh with this change and created a new docker image on top of the instantlinux/nut-upsd and supplanted my new entrypoint.sh. I was able to issue commands after that.
Completion checklist