Skip to content

Commit b57bc8c

Browse files
committed
lint
1 parent 8fd1a6a commit b57bc8c

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

coderd/database/dbmem/dbmem.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3749,7 +3749,7 @@ func (q *FakeQuerier) GetProvisionerDaemonsByOrganization(_ context.Context, arg
37493749
return daemons, nil
37503750
}
37513751

3752-
func (q *FakeQuerier) GetProvisionerDaemonsWithStatusByOrganization(ctx context.Context, arg database.GetProvisionerDaemonsWithStatusByOrganizationParams) ([]database.GetProvisionerDaemonsWithStatusByOrganizationRow, error) {
3752+
func (q *FakeQuerier) GetProvisionerDaemonsWithStatusByOrganization(_ context.Context, arg database.GetProvisionerDaemonsWithStatusByOrganizationParams) ([]database.GetProvisionerDaemonsWithStatusByOrganizationRow, error) {
37533753
err := validateDatabaseType(arg)
37543754
if err != nil {
37553755
return nil, err

docs/admin/monitoring/logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Connect logs are all captured in the `coderd` logs.
2525
## `provisionerd` Logs
2626

2727
Logs for [external provisioners](../provisioners.md) are structured
28-
[and configured](../../reference/cli/provisioner_start.md#--log-human) similarly
28+
[and configured](../../reference/cli/provisioners_start.md#--log-human) similarly
2929
to `coderd` logs. Use these logs to troubleshoot and monitor the Terraform
3030
operations behind workspaces and templates.
3131

docs/admin/provisioners.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ For example, running 30 provisioner containers will allow 30 users to start
2828
workspaces at the same time.
2929

3030
Provisioners are started with the
31-
[`coder provisioner start`](../reference/cli/provisioner_start.md) command in
31+
[`coder provisioner start`](../reference/cli/provisioners_start.md) command in
3232
the [full Coder binary](https://github.com/coder/coder/releases). Keep reading
3333
to learn how to start provisioners via Docker, Kubernetes, Systemd, etc.
3434

@@ -235,7 +235,7 @@ This is illustrated in the below table:
235235

236236
Provisioners can broadly be categorized by scope: `organization` or `user`. The
237237
scope of a provisioner can be specified with
238-
[`-tag=scope=<scope>`](../reference/cli/provisioner_start.md#-t---tag) when
238+
[`-tag=scope=<scope>`](../reference/cli/provisioners_start.md#-t---tag) when
239239
starting the provisioner daemon. Only users with at least the
240240
[Template Admin](./users/index.md#roles) role or higher may create
241241
organization-scoped provisioner daemons.
@@ -245,7 +245,7 @@ There are two exceptions:
245245
- [Built-in provisioners](../reference/cli/server.md#--provisioner-daemons) are
246246
always organization-scoped.
247247
- External provisioners started using a
248-
[pre-shared key (PSK)](../reference/cli/provisioner_start.md#--psk) are always
248+
[pre-shared key (PSK)](../reference/cli/provisioners_start.md#--psk) are always
249249
organization-scoped.
250250

251251
### Organization-Scoped Provisioners

0 commit comments

Comments
 (0)