oci ce node-pool update sends extra "nodeConfigDetails" in the put body caused 400
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
oci ce node-pool update --node-pool-id ocid1.nodepool.oc1.phx.xxx --node-source-details '{"imageId": "ocid1.image.oc1.phx.xx", "sourceType": "IMAGE"}' --debug
It returns 400. As you can see in the debug output, the put body has an extra field in JSON "nodeConfigDetails": {} that caused the 400.
Contributor guide
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
Reproduce the oci ce node-pool update command with --debug and inspect the PUT body shown in the output. Trace the node-pool update request serialization to find why an empty nodeConfigDetails field is included. Done means the field is omitted when unused and the command no longer returns the reported 400 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100