TritonDataCenter / TritonDataCenter/node-triton
prefer `tls_insecure` to `insecure` in profile json
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
When configuring node-triton via envvars we use the descriptive TRITON_TLS_INSECURE, but in json we use the mysteriousinsecure. This is likely a holdover from translating the smartdc toolset.
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
Search the profile JSON handling and references to the insecure option, then compare them with the TRITON_TLS_INSECURE environment-variable path. Update the profile configuration name to tls_insecure and verify that profile-based configuration uses the descriptive name consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, cloud
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100