TritonDataCenter / TritonDataCenter/node-triton
Set TRITON_* env vars via `triton env`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
triton env sets a number of useful environment variables so that other applications can interact with Triton based on the selected (or specified) profile in node-triton. For example:
$ triton env us-east-1
# triton
export TRITON_PROFILE="us-east-1"
# docker
export DOCKER_CERT_PATH=<path>
export DOCKER_HOST=tcp://us-east-1.docker.joyent.com:2376
export DOCKER_TLS_VERIFY=1
export COMPOSE_HTTP_TIMEOUT=300
# smartdc
export SDC_URL="https://us-east-1.api.joyent.com"
export SDC_ACCOUNT="<username>"
unset SDC_USER
export SDC_KEY_ID="<key fingerprint>"
unset SDC_TESTING
# Run this command to configure your shell:
# eval "$(triton env us-east-1)"
The typical consumer of these vars has been understood to be the Docker CLI and legacy smartdc tools, but other consumers can include Hashicorp's Terraform and Packer, as well as other tools. It would be very preferable to use TRITON_* variables in those applications, rather than the legacy SDC_* variable names. Perhaps the following could all be set?
# triton
export TRITON_PROFILE="us-east-1"
export TRITON_URL="https://us-east-1.api.joyent.com"
export TRITON_ACCOUNT="<username>"
unset TRITON_USER
export TRITON_KEY_ID="<key fingerprint>"
unset TRITON_TESTING
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the implementation of triton env and its existing profile-to-environment mapping. Compare the current SDC output with the requested TRITON_* values, then run the command with a selected profile and verify the rendered exports and unsets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100