cloudflare / cloudflare/cloudflared

💡 option in cloudflared service install to not start cloudflared

Open
#1,706 1 comment 0 reactions 0 assignees View on GitHub
Priority: Normal Type: Feature Request
Dominant language
Go
Stars
15.6k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

**Describe the feature you'd like**
When using `cloudflared service install`, `cloudflared` also attempts to start the start the service (equivalent to `systemd enable --now [service]`. For our use case, where we are provisioning devices its faster to not have to wait for cloudflared to come up (and also we see some transient errors where a timeout can happen and fail the entire process.

**Describe alternatives you've considered**
We could installed the systemd service ourselves, but I think this option would benefit others and also ensure our unit files are always up to date.

Contributor guide

Open the contributing guide

Research direction

Start at the implementation of `cloudflared service install` and inspect how the service is started after installation, along with any existing service-install tests. Done means an option can install and enable the service without starting `cloudflared`, while the current default behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.