Updating factbook.yaml to get factbook_compliant in Policy Engine - #155
Open
medidata wants to merge 2 commits into
Open
Updating factbook.yaml to get factbook_compliant in Policy Engine#155medidata wants to merge 2 commits into
medidata wants to merge 2 commits into
Conversation
Policy Engine will be live soon and will block PRs for non factbook_compliant repos. # Changes Made: We gathered data from various sources. Please verify if the data in the PR is correct and if that is wrong, feel free to add a commit to correct the data. Policy engine expects experience, product and team information to be present in the factbook.yaml file to mark the repo to be compliant. # Impact: This is just a METADATA file change which is consumed by DevOps central and there would be no other code change we are requesting for. Hence, looking forward to getting this PR reviewed and merged after verification and correction of the data. # Contact: Please reach out to [ops-dev-enablement](https://app.slack.com/channels/C08L42T5WJ2)
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a factbook.yaml Backstage Component descriptor so the repository can be evaluated as “factbook_compliant” by Policy Engine / DevOps central tooling.
Changes:
- Introduces a new
factbook.yamlwith BackstageComponentmetadata. - Adds team, people, annotations, channels, and
specfields intended to satisfy compliance checks.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+28
to
+30
| type: FIX_TYPE | ||
| lifecycle: FIX_REQUIRED_LIFECYCLE | ||
| owner: FIX_REQUIRED_OWNER |
Comment on lines
+5
to
+6
| name: FIX_REQUIRED_NAME | ||
| description: FIX_REQUIRED_DESCRIPTION |
Comment on lines
+10
to
+11
| - role: product owner | ||
| email: Not Found in Factbook |
Comment on lines
+20
to
+24
| - url: FIX_REQUIRED_CHANNEL_URL | ||
| role: slack | ||
| automated_messaging: true | ||
| mention: FIX_REQUIRED_SLACK_MENTION | ||
| - url: FIX_REQUIRED_EMAIL_CHANNEL_URL |
glow-mdsol
approved these changes
Jun 12, 2026
glow-mdsol
left a comment
glow-mdsol
left a comment
Member
There was a problem hiding this comment.
Documentation updates, no code changes
jimkont
approved these changes
Jun 12, 2026
This file contains hidden or 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
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.
Background:
Policy Engine will be live soon and will block PRs for non factbook_compliant repos.
Changes Made:
We gathered data from various sources. Please verify if the data in the PR is correct and if that is wrong, feel free to add a commit to correct the data.
Policy engine expects experience, product and team information to be present in the factbook.yaml file to mark the repo to be compliant.
Impact:
This is just a METADATA file change which is consumed by DevOps central and there would be no other code change we are requesting for. Hence, looking forward to getting this PR reviewed and merged after verification and correction of the data.
Contact:
Please reach out to ops-dev-enablement