search

elastic / connectors-ruby

Official Connector Clients for Elastic Elasticsearch, Enterprise Search, App Search and Workplace Search
https://www.elastic.co/guide/en/enterprise-search/master/index.html
Other
9 stars 17 forks source link

Create catalog-info file #566

Closed elastic-backstage-prod[bot] closed 11 months ago

elastic-backstage-prod[bot] commented 11 months ago

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[bot] commented 11 months ago

❌ Author of the following commits did not sign a Contributor Agreement: 1084ba9a226cbd0581354f260496df0ba5844823

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

github-actions[bot] commented 11 months ago

💔 Failed to create backport PR(s)

Status Branch Result
❌ 8.11 The branch "8.11" is invalid or doesn't exist

To backport manually run: backport --pr 566 --autoMerge --autoMergeMethod squash