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

[Bug]: Adding an ExtensionActionScope for ArmProviderAction op template #2324

Open
4 tasks done
allenjzhang opened this issue Mar 6, 2025 · 0 comments
Open
4 tasks done
Labels
bug Something isn't working needs-area

Comments

@allenjzhang
Copy link
Member

allenjzhang commented Mar 6, 2025

Describe the bug

FileShare raised an awareness that common ARM internal APIs has a pattern for extension resource provider level action.

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{sourceResourceProviderName}/{sourceResourceProviderType}/{sourceResourceName}/providers/Microsoft.FileShares/notify

Proposed adding following extension resource action scope to produce

/{resourceUri}/providers/Microsoft.FileShares/notify

@armVirtualResource
@extensionResource
model ExtensionResourceActionScope {
  @doc("Symbolic name of scope")
  @path
  @visibility(Lifecycle.Read)
  @key
  @segment("extensionresource")
  name: string;
}

Reproduction

Playground

Checklist

  • Follow our Code of Conduct
  • Check that this issue is about the Azure libraries for typespec. For bug in the typespec language or core libraries file it in the TypeSpec repo
  • Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.
@allenjzhang allenjzhang added the bug Something isn't working label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-area
Projects
None yet
Development

No branches or pull requests

1 participant