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

Using todo templates with Azure free trial subscription #1460

Closed
vhvb1989 opened this issue Jan 26, 2023 · 7 comments
Closed

Using todo templates with Azure free trial subscription #1460

vhvb1989 opened this issue Jan 26, 2023 · 7 comments
Assignees

Comments

@vhvb1989
Copy link
Member

vhvb1989 commented Jan 26, 2023

This issue is meant to define what's the experience for a customer when trying azd with a fresh new created Azure Free trial subscription.

There are some settings defined on the todo templates, like the SKU for a service-plan which are only available on a specific region for a free trial subscription. For example, trying to call azd up -t todo-python-mongo with the free trial sub and using the default Location East US 2 would lead the users to an error like:

"code": "SubscriptionIsOverQuotaForSku",
"message": "This region has quota of 0 instances for your subscription. Try selecting different region or SKU."

Then, switching to region East US works. But, as a new customer, how do I know what region/settings to use when I am using the free trial? Or how do I know which templates are 100% usable for my subscription?

--
Some ideas:

  • consider creating templates with FREE sku options, as well as potentially adding a "tag" to the templates stating what the minimum Subscription type can be used i.e. FREE, Trial, Edu etc.
@ghost ghost added the needs-triage For new issues label Jan 26, 2023
@ghost ghost removed the needs-triage For new issues label Jan 30, 2023
@rajeshkamal5050 rajeshkamal5050 added this to the Release 0.8 milestone Jan 30, 2023
@puicchan
Copy link
Contributor

Default region was selected because of capacity issue. Since we can't accurately predict/get the right region with capacity, my suggestion is to default to "east us" instead of "east us 2" to reduce issue for folks with free trial subscription.

@ciwchris
Copy link

ciwchris commented Feb 1, 2023

I experienced this using my MSDN subscription. It finally worked with "East US", I think it was the 4th region I tried. It was a frustrating experience.

@rajeshkamal5050
Copy link
Contributor

Related issue #1568 when LocationNotAvailableForResourceType

@pamelafox
Copy link
Member

Noting the experience from the workshop I ran, since it's related to this issue. In my workshop, they were trying to deploy https://github.com/pamelafox/simple-fastapi-azure-function to Azure Functions + APIM.

  1. When they first tried azd up, they got: "ERROR: reading subscription id: please provide options to select from" As it turns out, they hadn't made a subscription. So I think it's really important for workshops to stress that folks need both an account and a subscription. I also think that error could be more newbie-friendly (I can file an issue for that- i.e. "If you don't yet have a subscription, you can create one in the portal.")

  2. They then got a subscription, and I think they may have had to redo the auth login to get it to find the subscription ID. If thats the case, it might help to add an explicit instruction to above error message about that.

  3. Then when they tried to up, they got this error: "Deployment Error Details:

Unauthorized: This region has quota of 0 instances for your subscription. Try selecting different region or SKU.

  • This region has quota of 0 instances for your subscription. Try selecting different region or SKU." I haven't figured out which service was restricting them, so I wasn't sure what region to select. I did tell them how to find the .env file and change the location, but it might be annoying to try a bunch of locations. Not sure quite what to do about this. It'd be nice if it was easier to change location (something easier than digging for the .env file)

@savannahostrowski
Copy link

Related to #468; moving to Gallium as this is non-blocking for GA

@rajeshkamal5050
Copy link
Contributor

@ellismg @vhvb1989 Explore validate API and see if it helps alleviating some of these issues?

@vhvb1989
Copy link
Member Author

vhvb1989 commented Sep 2, 2023

validate API

The ValidateAPI checks the syntaxis. I don't think it would be able to help here:

Validates whether the specified template is syntactically correct and will be accepted by Azure Resource Manager

https://learn.microsoft.com/en-us/rest/api/resources/deployments/validate.

Template's owner should know about any limitations (like region/sub/etc) and describe those limitations within the infra files (bicep).
For example, using @allowed annotation to set what locations will work

@vhvb1989 vhvb1989 closed this as completed Sep 2, 2023
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

7 participants