Skip to content

docs: Add guide for working with loft-sh/api types#3720

Open
pascalbreuninger wants to merge 3 commits into
mainfrom
claude/slack-check-api-dependency-update-sQmn5
Open

docs: Add guide for working with loft-sh/api types#3720
pascalbreuninger wants to merge 3 commits into
mainfrom
claude/slack-check-api-dependency-update-sQmn5

Conversation

@pascalbreuninger
Copy link
Copy Markdown
Member

What issue type does this pull request address?
/kind documentation

What does this pull request do? Which issues does it resolve?

This PR adds comprehensive documentation to the CONTRIBUTING.md file explaining how to work with types from the github.com/loft-sh/api/v4 package when developing vCluster locally.

The new section covers:

  • Why the workflow matters (schema generation dependencies)
  • Step-by-step local development workflow for testing API type changes
  • Instructions for using replace directives in go.mod for local testing
  • The proper merge order when changes span both loft-enterprise and vCluster repositories
  • How to ensure both repositories stay in sync

This documentation helps contributors understand the dependency relationship between vCluster and loft-enterprise, and provides clear guidance on the correct process for making and testing changes to shared API types.

Please provide a short message that should be published in the vcluster release notes

N/A - Documentation only

What else do we need to know?

This is a documentation-only change that adds a new section to CONTRIBUTING.md. No code changes or testing required.

E2E Tests

No testing needed - documentation only.

none

https://claude.ai/code/session_01L1AZrxEXzRecXFpimzP8gD

Document the process for making changes to github.com/loft-sh/api/v4
types (in loft-enterprise) and testing them locally in vCluster before
merging. This addresses the chicken-and-egg dependency issue where
schema changes require coordinated updates across repositories.

https://claude.ai/code/session_01L1AZrxEXzRecXFpimzP8gD
@pascalbreuninger pascalbreuninger requested a review from a team as a code owner March 19, 2026 15:58
Comment thread CONTRIBUTING.md Outdated

### 4. Test Your Changes

Deploy a vCluster with your schema changes and verify the new configuration options work as expected.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step needs more clarification.

I have changes in /path/to/loft-enterprise/staging/src/github.com/loft-sh/api/v4 that I have to test in the platform, so after completing steps 1-3 above, I want to create a virtual cluster from the platform, and here I want to use local vCluster changes (so it uses locally changed schema from step 3 above).

claude added 2 commits March 31, 2026 07:57
Address PR review feedback from @nprokopic requesting more detail on
how to actually test local vCluster changes from the platform. Added
steps for building a custom Docker image and deploying it with a
local chart using --local-chart-dir.

https://claude.ai/code/session_01L1AZrxEXzRecXFpimzP8gD
The previous version incorrectly suggested using --local-chart-dir for
platform testing. This flag only works with the Helm driver. When
testing schema changes through the platform driver, intermediate
pre-releases are required because the platform fetches charts from
published releases. Updated docs to clearly separate the two workflows
and document the version coupling implications.

https://claude.ai/code/session_01L1AZrxEXzRecXFpimzP8gD
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants