TritonDataCenter / TritonDataCenter/node-triton
`triton profile rm -f NAME` sometimes still doesn't remove it
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
root@7e13a025-7d2a-c988-99b3-a91082c6b52a:~# triton profile ls
NAME CURR ACCOUNT USER URL
lximgtest * lximgtest - https://10.88.88.5
root@7e13a025-7d2a-c988-99b3-a91082c6b52a:~# triton profile rm -f lximgtest
triton profile: error (Config): could not load "env" profile (missing TRITON_*, or SDC_*, environment variables)
root@7e13a025-7d2a-c988-99b3-a91082c6b52a:~# triton profile ls
NAME CURR ACCOUNT USER URL
lximgtest * lximgtest - https://10.88.88.5
It should still delete in this case.
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
Start by tracing the triton profile rm -f NAME command and how it loads profiles, focusing on the failure to load the env profile. Done means the named profile is removed even when the environment variables are missing, and triton profile ls no longer lists it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100