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

The new swagger generated using TSP lacks API endpoint definitions #5077

Open
melina5656 opened this issue Feb 14, 2025 · 0 comments
Open

The new swagger generated using TSP lacks API endpoint definitions #5077

melina5656 opened this issue Feb 14, 2025 · 0 comments
Labels
openapi-to-tsp Tracks OpenAPI to Cadl converter issues

Comments

@melina5656
Copy link
Member

Describe the bug

I used the npx tsp client convert -- swagger readme [path to readme. md] -- arm -- fully compatible command to generate a new TSP project, and the main.tsp shows that the version of @autorest/openapi-to-typespec I am using is 0.10.9.
Two API endpoint definitions are missing from the generated swagger from the TSP project. "operationId": "ManagedHsmKeys_ListVersions" and "operationId": "Keys_ListVersions"

The original swagger:
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/keyvault/resource-manager/Microsoft.KeyVault/stable/2024-11-01/keysManagedHsm.json#L232
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/keyvault/resource-manager/Microsoft.KeyVault/stable/2024-11-01/keys.json#L288

Expected behavior
The new swagger should have the same API endpoint definition as the old swagger

Actual behavior
Missing "operationId": "ManagedHsmKeys_ListVersions" and "operationId": "Keys_ListVersions"

@pshao25 pshao25 added the openapi-to-tsp Tracks OpenAPI to Cadl converter issues label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
openapi-to-tsp Tracks OpenAPI to Cadl converter issues
Projects
None yet
Development

No branches or pull requests

2 participants