TritonDataCenter / TritonDataCenter/node-triton
want `triton profile create --insecure` to be able to setup a profile to a cloudapi with self-signed cert
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
E.g. for dev/testing DCs. Also docs around insecure:true.
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 create --insecure command and the existing insecure:true configuration handling. Confirm how profiles connect to a cloudapi with a self-signed certificate, then update the command behavior and document the insecure setting; done means the profile can be created and the usage is explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, cloud, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100