New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add API endpoints for Nutanix categories #9466
Add API endpoints for Nutanix categories #9466
Conversation
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Skipping CI for Draft Pull Request. |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: embik, maciaszczykm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: c1fdf3bbf4454559702e04e4ec3d869e90916977
|
/retest |
What does this PR do / Why do we need it:
This PR adds the following KKP API endpoints:
/v2/providers/nutanix/{dc}/categories
for category keys/v2/projects/{project_id}/clusters/{cluster_id}/providers/nutanix/categories
for category keys via cluster credentials/v2/providers/nutanix/{dc}/categories/{category}/values
for category values/v2/projects/{project_id}/clusters/{cluster_id}/providers/nutanix/categories/{category}/values
for category values via cluster credentialsThey are needed so the dashboard can offer autocompletion for Nutanix categories when creating MachineDeployments. That is important because categories do not exactly work like tags (in other providers): Only pre-existing category keys (names) and values can be used. So the dashboard should only offer categories and respective values that exist already.
Does this PR close any issues?:
Fixes #8927
Special notes for your reviewer:
Documentation:
Does this PR introduce a user-facing change?: