security/tailscale: add description to restart service
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- php
- Domain
- infrastructure
Research direction
The restart action is defined in the tailscale plugin under security/tailscale, most likely in an actions config file such as actions_tailscale.conf. Compare it with another plugin's actions file that already has a description, then add the missing description to the restart entry. Done when the action shows a description in the OPNsense Actions list.
Written by the indexing model from the issue text.
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
I just need to be able to restart Tailscale using cron/actions. I saw that the Tailscale restart config is missing a description which is required by OPNsense actions.
Describe the solution you'd like
Add a simple description for the restart action.
Describe alternatives you've considered
None. Service restart requires sudo.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 896
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opnsense/plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
security/acme-client: missing accounts directory causes DNS-01 validation failureMay be free again A pull request for this issue was closed without being merged. Opensupport
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
opnsense/plugins#5770 · 1 comment ·
Maintainers usually reply within 1 day
-
security/tor: Advanced mode / help toggles are brokenPossibly taken @txr13 claimed this 43 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
os-opnproxy 1.0.5_5Openincomplete
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
opnsense/plugins#5710 · 1 comment ·
Maintainers usually reply within 1 day
-
net/vnstat: use OPNsense interface names in dashboard widgetPossibly taken @joeroback claimed this 106 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in opnsense/plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jwage/phpamqplib-messenger#163 ·
-
Newsletter subscription page logs Undefined array key "nw_error" on every GETPossibly taken @Codencode claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
PrestaShop/ps_emailsubscription#145 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
jira-created
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 78/100