TritonDataCenter / TritonDataCenter/sdc-cloudapi
AddNic should accept a "primary" argument
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 22
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently when creating a new nic with AddNic via cloudapi, it's not possible to make the new NIC the "primary" NIC for the VM. This is quite frustrating, since there is no other mechanism to make a NIC primary after creation through cloudapi either. Our users currently end up having to file tickets to get us to go and correct the situation by hand.
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 at the cloudapi AddNic endpoint and trace how NIC creation handles request arguments. The work is done when AddNic accepts a "primary" argument and can create the new NIC as the VM's primary NIC, with the behavior covered by the relevant API tests if they exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100