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
decide how to handle nesting of agents in resources and ports in agents - subrows? Just rich cells?
build resources table component with columns for Resource, Lifetime, Status, and Access. (Lifetime (persistent or ephemerial) is in the Status column in the image but will be separated out)
nest agents in resources and ports in agents
design Access cell to always have Open in Terminal, and always have Any Port button where you can open any port on that agent. Also have any dev urls/applications that are assigned to that agent and a specific port. However, building Open in Terminal links and DevURL/application links are taken care of in other tickets.
Consider having Any Port show which ports are already assigned.
Dev URLs will be added to this later (same endpoint).
Desired (follow-up): open resource in terminal. We need to create another ticket for that.
Step 1
Present the data similarly to the CLI in a table.
Step 2
We're going to clean up the UI (TBD)
Step 3
Dev URLs
Job associated to WorkspaceResource (job created resource)
Workspace and WorkspaceResource do not have a relationship (job creates the resource)
Type can be presented verbatim
Name can be presented verbatim
Agents - Running process attached to resource. (example coder agent running within v2 while dogfooding).
Request --> We can safely poll without 4xx or 5xx, because the data is static (not actually touching the workspace itself). The FE can remain open and continue to poll.
"Desired (follow-up): open resource in terminal. We need to create another ticket for that." @code-asher isn't this essentially #760? It's just that instead of having one terminal link like in v1 there's one per workspace agent as shown here.
"Desired (follow-up): open resource in terminal. We need to create another ticket for that." @code-asher isn't this essentially #760? It's just that instead of having one terminal link like in v1 there's one per workspace agent as shown here.
lifecycle is computed on the frontend - we get what resources exist in Stop and what exist in Start, and those that exist in Start but not Stop, they're ephemeral (gets destroyed on Stop). query the template version for its resources. can't query workspace build bc it only shows for the state it's currently in. will get a flat array where each item is a resource with a workspace transition, so need to look for the resource by its name and type and see if the array has one with stop and one with start. prob a nice to have.
@BrunoQuaresma that's what I meant by "I'm going to take out Lifecycle and Access" - I just put them in for the screenshot so we could all be on the same page about how it will look eventually. DevURLs and apps will go in the Access column.
Activity
[-]Resources Card[/-][+]Frontend Workspace Resources Card[/+]misskniss commentedon Apr 26, 2022
There is a meeting on the calendar to discuss this one for details.
misskniss commentedon Apr 26, 2022
Hey team! Please add your planning poker estimate with ZenHub @presleyp @kylecarbs
presleyp commentedon Apr 28, 2022
table of resources with ability to open each in web terminal
Button on each row called Open In Terminal
presleyp commentedon Apr 28, 2022
persistent/ephemeral is a different type of data than connection status. can call that column Lifetime?
presleyp commentedon Apr 28, 2022
subrows: could make it monospace and use the ascii elbow
presleyp commentedon Apr 28, 2022
Open Port button - opens dropdown where you type port number
DevURLs are predefined port allocations (and use a certain resource)
But resources can be opened in any port. If you open dev in the port VSCode is assigned to, you see VSCode.
presleyp commentedon Apr 28, 2022
Look into nesting dev urls/applications in resources card
Resource - Agent - Ports (some are apps, can also open any port)
presleyp commentedon Apr 28, 2022
make agent connection status optional so we can reuse this component for a preview
8 remaining items
greyscaled commentedon May 11, 2022
Breakout session notes
coder/cli/show.go
Lines 11 to 39 in 982769f
coder/codersdk/workspacebuilds.go
Lines 61 to 72 in 982769f
The API:
coder/codersdk/workspaceresources.go
Lines 23 to 31 in 537897c
Dev URLs will be added to this later (same endpoint).
Desired (follow-up): open resource in terminal. We need to create another ticket for that.
Step 1
Present the data similarly to the CLI in a table.
Step 2
We're going to clean up the UI (TBD)
Step 3
Dev URLs
Job associated to WorkspaceResource (job created resource)
Workspace and WorkspaceResource do not have a relationship (job creates the resource)
Type can be presented verbatim
Name can be presented verbatim
Agents - Running process attached to resource. (example coder agent running within v2 while dogfooding).
Request --> We can safely poll without 4xx or 5xx, because the data is static (not actually touching the workspace itself). The FE can remain open and continue to poll.
presleyp commentedon May 12, 2022
"Desired (follow-up): open resource in terminal. We need to create another ticket for that." @code-asher isn't this essentially #760? It's just that instead of having one terminal link like in v1 there's one per workspace agent as shown here.
presleyp commentedon May 12, 2022
And adding Dev URLs is #805
code-asher commentedon May 12, 2022
Yup I think #760 is perfect for this
greyscaled commentedon May 16, 2022
We're currently blocked on this (@deansheather 's working on something)
presleyp commentedon May 17, 2022
lifecycle is computed on the frontend - we get what resources exist in Stop and what exist in Start, and those that exist in Start but not Stop, they're ephemeral (gets destroyed on Stop). query the template version for its resources. can't query workspace build bc it only shows for the state it's currently in. will get a flat array where each item is a resource with a workspace transition, so need to look for the resource by its name and type and see if the array has one with stop and one with start. prob a nice to have.
presleyp commentedon May 17, 2022
Agents will have an array of Apps soon, and status. WorkspaceApp will have external URL and I just need to render name, icon, and a link to that url.
presleyp commentedon May 18, 2022
I'm going to take out Lifecycle and Access for this ticket but here's where I envision them:
tjcran commentedon May 20, 2022
@BrunoQuaresma this is an example of what would go above the timeline in #1620
BrunoQuaresma commentedon May 20, 2022
Ok. How are we going to add DEV URLs and apps inside of this?
BrunoQuaresma commentedon May 20, 2022
What do you think about removing the
Coming soonfields to not look "incomplete"?presleyp commentedon May 20, 2022
@BrunoQuaresma that's what I meant by "I'm going to take out Lifecycle and Access" - I just put them in for the screenshot so we could all be on the same page about how it will look eventually. DevURLs and apps will go in the Access column.