Azure / Azure/azure-rest-api-specs

[TSV][Bug] Fix the missing configuration for current repo so it won't block normal customers

Open
#34,211 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 37m
Merged PRs (30d)
446

Description

SDK team is trying to add missing `tspconfig.yaml` for `workloads/Workloads.SAPVirtualInstance.Management` in our April release but we found the tsv checked all 4 libs under the same `workloads` folder. Since other 3 haven't have language configurations yet so we failed with [TypeSpec Validation and the log is here](https://github.com/Azure/azure-rest-api-specs/actions/runs/14638819466/job/41076137512#logs).

- [pr link](https://github.com/Azure/azure-rest-api-specs/pull/33826)

![Image](https://github.com/user-attachments/assets/47697f29-6964-4487-8dc6-54f0c9d47260)

I think ultimately all spec should have configs but for now spec repos have some missing configurations libs, Could eng team have one-time fix for them?

Otherwise pr authors will be blocked by failures that is un-relevant to current services. Also I am curious why we include all libs under the same RP, any reasons to do that?

Contributor guide

Open the contributing guide

Research direction

Start with workloads/Workloads.SAPVirtualInstance.Management/tspconfig.yaml and the TypeSpec Validation log from the linked workflow run; compare the four libraries under workloads and the related pull request. Done means the April-release configuration can be validated without unrelated libraries lacking language configurations blocking the change.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
build-system, ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.