openshift / openshift/machine-config-operator

move types to openshift/api

Open
#588 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

lifecycle/frozen
Dominant language
Go
Stars
269
Forks
529
Avg merge
3d 18h
Merged PRs (30d)
83

Description

Types other than the machineconfig type should live in openshift/api and clients generated for them over there. See https://github.com/openshift/api/issues/216.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the type definitions in this repository and the linked openshift/api issue 216 to identify which types are not machineconfig types and where their clients are generated. Done means those types live in openshift/api and their clients are generated there, while the machineconfig type remains here.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.