Skip to content

Bootstrap repository#945

Merged
pickypg merged 4 commits intomainfrom
add-catalog-info
Feb 14, 2026
Merged

Bootstrap repository#945
pickypg merged 4 commits intomainfrom
add-catalog-info

Conversation

@elastic-backstage-prod
Copy link
Copy Markdown
Contributor

⚠️ This is only relevant for Elastic employees, there are some links pointing to some internal GitHub repositories and docs.

If you already have a ./catalog-info.yaml file defined in your repository, you probably want to close this PR.

If not - this PR provides you with the scaffolding for one. The catalog-info.yaml file is where you can define your infrastructure needs (such as Buildkite pipelines) in the form of Real Resource Entities.


If you already have a Buildkite pipeline defined in the elastic/ci repository, you can copy its definition in this catalog-info.yaml file (see instructions).

Once the pipeline definition is ingested into Backstage, Terrazzo will emit a warning about a duplicate definition with a warning similar to:
🙈 Ignoring remote manifest in favour of local one: buildkite.elastic.dev/v1=>Pipeline=> your-pipeline

At this point, it is safe for you to delete the Pipeline definition from the elastic/ci repository.

This PR was raised by @pickypg.

@pickypg pickypg merged commit d917654 into main Feb 14, 2026
5 checks passed
@pickypg pickypg deleted the add-catalog-info branch February 14, 2026 00:09
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.

1 participant