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.

Sign up for GitHub

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

Jump to bottom

Operation id in description is not correct #4831

Closed
pshao25 opened this issue Jun 18, 2024 · 1 comment
Closed

Operation id in description is not correct #4831

pshao25 opened this issue Jun 18, 2024 · 1 comment
Assignees
@pshao25
Labels
Mgmt This issue is related to a management-plane library.

Comments

@pshao25
Copy link
Member

pshao25 commented Jun 18, 2024

Symptom:
Some diff exists in swagger generated SDK and tsp generated SDK.
image

Root cause:
The operation id from swagger is like interface/namespace_operationname.

The operation id from tsp is simply resourcename_operationname

Solution:

  1. Pass the operation id from spec to generator, which would change the public contract API.
  2. When deserialize InputOperation get information from InputClient. Is this possible?
@chunyu3 chunyu3 added the Mgmt This issue is related to a management-plane library. label Jun 26, 2024
@pshao25
Copy link
Member Author

pshao25 commented Jun 26, 2024

As discussed, we don't fix it for now.

@pshao25 pshao25 closed this as completed Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pshao25 pshao25

Labels
Mgmt This issue is related to a management-plane library.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chunyu3 @pshao25