add OXIDE_PROJECT, OXIDE_VPC etc to stop always having to type --project, --vpc etc...

[Smithx10]

Target component

• CLI
• SDK
• Something else
• Not sure

Overview

When using the CLI I'd like to be able to provide --vpc or --project as an env var or set them via the cli. Having to always provide --vpc or --project interrupts me from just typing commands. In my workflow I'm typically going to be working within a project... so being able to quickly oxide inst list, or oxide vpc list without having to type --project or always have to ctrl + r back. If there is a way to currently do this, I apologize in advance for opening this.

Implementation details

No response

Anything else you would like to add?

No response

[ahl]

This is a great idea; I'm going to look into some options regarding how we make this sort of default easy to specify.

[sudomateo]

Just thinking out loud a bit. Perhaps we can use profiles to implement a default project.

> cat ~/.config/oxide/credentials.toml
[profile.foo]
host = "https://oxide.example.com"
token = "oxide-token-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
user = "febdc6fe-3ba8-4d14-b17c-5b5bdc640e92"
project = "bar"

Or expose it in config.toml.

> cat ~/.config/oxide/config.toml
default-profile = "foo"
default-project = "bar"

[wfchandler]

We'd want to scope default-project to a given profile.

[bwagner5]

I wrote a little script that I use to do this until we have official support. There's some handling of omitting the default project ($OXIDE_PROJECT) when using an ID since the API errors (as mentioned in oxidecomputer/omicron#10517).

Here's the duct tape. I named it ox in my PATH:

#!/usr/bin/env bash
set -euo pipefail

uuid_re='^[0-9a-fA-F]{8}(-[0-9a-fA-F]{4}){3}-[0-9a-fA-F]{12}$'

for arg in "$@"; do
  case "$arg" in
    -h|--help|help|--project|--project=*) exec oxide "$@" ;;
  esac
  [[ "$arg" =~ $uuid_re ]] && exec oxide "$@"
done

if [ -n "${OXIDE_PROJECT:-}" ]; then
  exec oxide "$@" --project "$OXIDE_PROJECT"
fi

exec oxide "$@"