8000 Create catalog-info file by elastic-backstage-prod[bot] · Pull Request #43 · elastic/eui-cljs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Aug 13, 2024. It is now read-only.

Create catalog-info file #43

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Create catalog-info file #43

wants to merge 1 commit into from

Conversation

elastic-backstage-prod[bot]
Copy link

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.

@cla-checker-service CLA Checker Service
Copy link

❌ Author of the following commits did not sign a Contributor Agreement:
3d03a2b

Please, read and sign the above mentioned agreement if you want to contribute to this project

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants
0