Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Instance control for API Explorer #5595

Open
aweaver89 opened this issue Jan 13, 2025 · 0 comments
Open

Instance control for API Explorer #5595

aweaver89 opened this issue Jan 13, 2025 · 0 comments
Labels
feature Requests for new features. product/docs Fern Docs which builds and hosts a developer documentation site

Comments

@aweaver89
Copy link
Contributor

Feature Description

Right now there is limited control over the API Explorer at the instance level. It would be great to be able to flat out activate/disable the explorer per instance.

Use Case

We're working on building out our API Explorer and there is a lot of work to do. There is the possibility of disabling all API envs shown here, but 1. I'm not sure this actually disables the API explorer and 2) that's a lot more setup when I know that I just want to disable it flat out for one of my instances.

This way I could build things in my dev env and release it safely when ready.

Proposed Experience (Optional)

No response

Alternatives Considered (Optional)

No response
@aweaver89 aweaver89 added feature Requests for new features. product/docs Fern Docs which builds and hosts a developer documentation site labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Requests for new features. product/docs Fern Docs which builds and hosts a developer documentation site
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aweaver89