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

Schema for Microsoft.ApiManagement/service/templates incorrect #2176

Closed
kenmuse opened this issue Jan 13, 2022 · 1 comment
Closed

Schema for Microsoft.ApiManagement/service/templates incorrect #2176

kenmuse opened this issue Jan 13, 2022 · 1 comment

Comments

@kenmuse
Copy link

kenmuse commented Jan 13, 2022

The schema restricts template names to starting with names which have a lowercase first letter:

"enum": [
"applicationApprovedNotificationMessage",
"accountClosedDeveloper",
"quotaLimitApproachingDeveloperNotificationMessage",
"newDeveloperNotificationMessage",
"emailChangeIdentityDefault",
"inviteUserNotificationMessage",
"newCommentNotificationMessage",
"confirmSignUpIdentityDefault",
"newIssueNotificationMessage",
"purchaseDeveloperNotificationMessage",
"passwordResetIdentityDefault",
"passwordResetByAdminNotificationMessage",
"rejectDeveloperNotificationMessage",
"requestDeveloperNotificationMessage"

However, the service will report a 404 NotFound error when attempting to create or modify resources using these names. Each name must start with an uppercase letter to be accepted. Exporting an ARM template for an APIM resource will also show this issue; the names will start with an uppercase letter.
This also causes a problem defining the resources with Bicep templates. Those templates enforce the schema restrictions.

@anthony-c-martin
Copy link
Member

Thanks for reporting this! I've raised Azure/azure-rest-api-specs#17340 to track the root cause. Once fixed, schemas & bicep types will be automatically updated - closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants