Make it easier to create an instance within a non-default VPC/subnet

Open
#3,291 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start at the instance creation page and trace the existing default VPC and custom network interface flows. Define the simpler path for selecting another VPC and subnet, then verify that an instance can be created there without requiring a whole custom network interface.

Written by the indexing model from the issue text.

Description

The instance creation page allows you to either create an instance in the default VPC, or to create a whole custom network interface. If you want to create an instance in another VPC you are forced to go through the custom network interface. It'd be nice if there was an easier option for that.

Dominant language
TypeScript
Stars
228
Forks
22
Avg merge
19h 42m
Merged PRs (30d)
32

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oxidecomputer/console

All issues in oxidecomputer/console

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.