-
Notifications
You must be signed in to change notification settings - Fork 936
fix: make cli respect deployment --docs-url #14568
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
fix: make cli respect deployment --docs-url #14568
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @ethanndickson and the rest of your teammates on |
3ac949f
to
75cd7be
Compare
(No changes in previous push, just rebase) |
75cd7be
to
1c80204
Compare
If we're going to fetch the deployment config on startup, I think making it optional middlware, instead of making it part of say, |
I only just noticed these tests failed, because viewing deployment config is restricted - I still think just having a |
1c80204
to
87ea95c
Compare
Nah, I had to rethink it all - most admins are probably not giving regular users permissions to view the deployment config, so it needs to be included on I think I've missed a few doc links, so I'll get to those next |
24a9a36
to
4c276e6
Compare
This approach is definitely better, but since opening this PR we've added a docs link to a help command. We can't plumb the fetched appearance config there (nor would we want to do a fetch before a help command), so I'm not totally sure what to do about that. It would be nice if we could just an additional field to a local config, but the cli stores |
c9e34ea
to
5bfb3ad
Compare
5bfb3ad
to
57a7f5c
Compare
With #14548, it's a lot more likely for a user to see a documentation link when using the CLI.
Assuming admins of airgapped Coder deployments aren't giving regular users permission to view the deployment config, we'll need to make the docs URL available on the more permissive
/appearance
endpoint.