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

[typespec/azure-resource-manager] logical result path is undefined in ArmResourceActionAsync #1894

Open
ArcturusZhang opened this issue Nov 20, 2024 · 0 comments
Assignees
Labels
design:needed A design request has been raised that needs a proposal lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library
Milestone

Comments

@ArcturusZhang
Copy link
Member

When an async operation is performed using Azure-AsyncOperation, the final result of the operation is returned in the properties property in the ArmOperationStatus model, see the standards on ARM RPCs here

For example, when I write:

model Employee is TrackedResource<EmployeeProperties> {
  ...ResourceNameParameter<Employee>;
}

model EmployeeProperties {
  /** Age of employee */
  age?: int32;
}

model Result {
  /** Result of the action */
  result: string;
}

op actionAsync is ArmResourceActionAsync<Employee, void, Result>;

it now gives us:

finalResult: Result
finalEnvelopeResult: Result
envelopeResult: ArmOperationStatus
finalResultPath: undefined

Should we have finalResultPath as properties here?

@ArcturusZhang ArcturusZhang added the lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library label Nov 20, 2024
@markcowl markcowl added the design:needed A design request has been raised that needs a proposal label Nov 25, 2024
@markcowl markcowl added this to the Backlog milestone Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design:needed A design request has been raised that needs a proposal lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library
Projects
None yet
Development

No branches or pull requests

3 participants