Create catalog-info file #1406
Closed
Create catalog-info file #1406
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![elastic-backstage-prod[bot]](https://avatars.githubusercontent.com/u/6764390?s=60&v=4){kind=small}
|
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
|
Hi @pquentin . Could we submit this PR? |
|
We can't due to the CLA check. I'll resubmit it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you already have a
./catalog-info.yamlfile 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.yamlfile 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.yamlfile (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/cirepository.