• read resources from api
• 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.
• hook up all access buttons
• storybook
• test

Handled in other tickets:

• Access Column: 760 and 805
• Lifecycle Column: TBD