You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A customer wants to run a coder_app in their workspace and access a service via a fixed URL but not have it appear in the dashboard as a button. They can't use listening/shared ports because their deployment doesn't support wildcard domains.
One option is to allow users to hide coder_apps in the UI by adding a new attribute.
resource"coder_app""hidden-service-url" {
agent_id = coder_agent.dev.id
slug ="my-hidden-service"
command ="run service"...
hidden =true# defaults to false# or
button =false# defaults to true
}
This could ergonomically expand the ability to use workspaces as service providers.
The text was updated successfully, but these errors were encountered:
It has been previously discussed in #8326 and #11349. That discusses a slightly different use case where the app could be hidden by using a condition in terraform.
What if we just interpreted leaving the icon value empty as indicative of an app that shouldn't be displayed? We should probably still display it somehow so that we can convey the health of the app even if we make it obvious that it's not supposed to be interacted with in the traditional sense.
A customer wants to run a
coder_app
in their workspace and access a service via a fixed URL but not have it appear in the dashboard as a button. They can't use listening/shared ports because their deployment doesn't support wildcard domains.One option is to allow users to hide
coder_app
s in the UI by adding a new attribute.This could ergonomically expand the ability to use workspaces as service providers.
The text was updated successfully, but these errors were encountered: