This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Adding Backstage healthy engineering component file [ci skip] #4
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.
Overview
👋
This was an automated PR submitted on your behalf to help streamline the process of enrolling this repository in our new developer portal - backstage!
We need your help to update this configuration and merge this pull request into your trunk branch.
You can find more information in this backstage announcement.
What does “registering” an app in backstage mean?
Enrolling an app in backstage means adding your applications to the software catalog. Our goal is to build a one-stop solution for the developer workflow. In the future, Backstage will surface actionable information such as release statuses, security vulnerabilities, open pull requests and more. This will also serve as a great place for new team members to start onboarding. At a global level, we will be able to create a centralized system that can keep track of ownership and metadata for our software.
Next Steps
We tried to automate most of this process. There are still a couple of things that will need input from you or your team.
unknown
fields (such asspec.owner
). This should be the name of an existing tech team. See the tech team docs here.spec.type
is accurate. This can beservice
,website
,library
,event-driven-service
,terraform-module
, orterraform-repo
. If your app doesn’t fit into any of these categories, please reach out to us in #backstage-discussion in Slack.spec.lifecycle
is accurate. This can beservice
,production
,experimental
, ordeprecated
. If your app doesn’t fit into any of these categories, please reach out to us in #backstage-discussion in Slack.❓ If you have any questions or issues feel free to reach out at #backstage-discussion in Slack! Thank you for registering your app in backstage! 🙏