Fix invalid reference in Catalog schema

[leecalcote]

Signed-off-by: Lee Calcote lee.calcote@layer5.io

[gemini-code-assist]

Summary of Changes

Hello @leecalcote, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an invalid reference within the Catalog schema's OpenAPI definition. The change corrects how an internal schema component references an external definition, ensuring proper schema validation and adherence to OpenAPI best practices.

Highlights

• Schema Reference Correction: The $ref for CatalogData within schemas/constructs/v1alpha2/catalog/openapi.yml has been updated to correctly point to an internal component schema (#/components/schemas/catalog) instead of a direct relative file path (./catalog.json).
• New Component Definition: A new catalog component schema has been introduced under components/schemas in schemas/constructs/v1alpha2/catalog/openapi.yml. This new component now correctly references the external catalog.json file, providing a proper structure for the schema.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the OpenAPI schema for the Catalog construct to improve how external schema definitions are referenced. The change updates the $ref value for CatalogData to point to the catalog schema defined within the same file and introduces a new catalog schema that references an external catalog.json file.