ManageIQ / ManageIQ/kubeclient
Support dryRun for POST, PUT, PATCH, and DELETE
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 426
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Dry Run is now available as beta since Kubernetes v1.13.
This involves adding the dryRun query parameter to requests. I'm hesitant to jump in and add support for extra parameters to the various modifier _entity methods as I see some discussion around cleaning these up in #312.
I'm thinking #391 with the addition of the **opts to create_ and update_ will allow us to easily add a dryRun option to those methods.
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
Start by reading the approach proposed in #391 and the cleanup discussion in #312, then trace the create_, update_, and modifier _entity methods. Confirm how Kubernetes dry-run query parameters are represented in requests. Done means POST, PUT, PATCH, and DELETE operations can receive the dryRun option and send the dryRun query parameter without breaking existing calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100