Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow configurable apis/ folder structure to avoid path collisions

Open
#214 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Start by tracing the CLI's existing explicit output-path option and comparing it with the non-conflicting schemas/ layout mentioned in the issue. Define how crossplane-project.yaml should configure the apis/ template and what the default should be; done means resources with the same kind but different API groups generate into distinct, deterministic directories.

Written by the indexing model from the issue text.

Description

enhancement
What problem are you facing?

Generating APIs from an XRD or simple schema can conflict when two resources share the same kind but belong to different API groups. For example:

kubernetesclusters.onprem.example.com
kubernetesclusters.cloud.example.com

Both of these generate today into the same directory, apis/kubernetesclusters/, causing a conflict.

There is currently an option to specify the output path explicitly, but that doesn't scale for larger repositories or automated build tooling, where paths need to be derived consistently rather than set by hand.

How could Crossplane help solve your problem?

Allow conflict-free generation of XRD definitions from an XR or simple schema. Ideas:

  1. Add an option in crossplane-project.yaml to configure how the apis/ folder is populated, using a template string such as {{ groupElement[1] }}/{{ kindPlural }}. For example, this would resolve to:
apis/
  onprem/
    kubernetesclusters/
      definition.yaml
  cloud/
    kubernetesclusters/
      definition.yaml
  1. Default to a non-conflicting structure, similar to what schemas/ already uses.
Dominant language
Go
Stars
19
Forks
31
Avg merge
2d 12h
Merged PRs (30d)
52

Contributor guide

Open the contributing guide

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.

More from crossplane/cli

All issues in crossplane/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.