Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Se] Validate infoblurb functionality for TypeSpec conversion #7975

Open
mario-guerra opened this issue Sep 11, 2024 · 0 comments
Open

[Se] Validate infoblurb functionality for TypeSpec conversion #7975

mario-guerra opened this issue Sep 11, 2024 · 0 comments
Assignees
Labels
needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team.

Comments

@mario-guerra
Copy link
Member

Context

The TypeSpec team has a plan for converting existing Azure services to TypeSpec. The process involves manual refinement of TypeSpec files (TSPs), validation through human reviews, and various work items assigned to different teams for approval and automation. The primary goal is to ensure that the converted TypeSpec generates an OpenAPI specification functionally equivalent to the original, maintaining round-trip correctness.

Description

The Engineering Systems (EngSys) team needs to validate that the infoblurb functionality works correctly. The infoblurb is a message inserted into every brownfield PR for services not yet converted to TypeSpec. It should inform teams about the upcoming requirement to convert to TypeSpec and offer assistance, but it should not be flagged as a warning or error. This functionality must be verified to ensure it operates as intended.

@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team.
Projects
None yet
Development

No branches or pull requests

2 participants