Proposed OpenAPI spec changes for catalog administration

[pboyd]

Description

These are proposed changes to the API spec for the model catalog to support admin functions from the dashboard. Specifically, it adds:

• A new endpoint to preview changes to a catalog source
• Unified fields for specifying models to include/exclude
• Status and error fields for sources

This is not intended to be merged, but we can take these changes as a starting point for implementation.

How Has This Been Tested?

N/A

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages
• Automated tests are provided as part of the PR for major new functionalities; testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from pboyd. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rareddy]

fyi, @mturley @andrewballantyne

[mturley]

@pboyd @chambridge do we know the structure of these additional properties? I imagine this is where we pass our huggingface allowedOrganization and apiKey, or our yaml for yaml-type sources?

[pboyd]

Yes, that's correct. The YAML source takes a yamlCatalogPath key.

For Hugging Face, the final version should be pretty close to what @adysenrothman has in #1852 (this file).

[mturley]

The YAML source takes a yamlCatalogPath key.

that makes sense in the configmap since we'll also create a file containing the yaml in the configmap, but I'm referring to the stateless preview request - everything needs to be embedded here right? the user is inputting yaml they haven't saved yet so i don't think we have a path to refer to yet