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

Please optimize the time to build for this service #25991

Closed
geglne opened this issue Feb 28, 2019 — with docs.microsoft.com · 8 comments
Closed

Please optimize the time to build for this service #25991

geglne opened this issue Feb 28, 2019 — with docs.microsoft.com · 8 comments

Comments

Copy link

geglne commented Feb 28, 2019

I have deployed this service 8-10 times over the past 2-3 months. This service takes between 70-90 minutes to stand up. Unfortunately, this means I cannot build this in some of the automation tools that I use. I would like to build this using Terraform but it isn't offered by Hashicorp at this time due to various issues (broken APIs?).

When will this be fixed? Below are links to Hashicorp issues:

hashicorp/terraform-provider-azurerm#438
hashicorp/terraform-provider-azurerm#869


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@AjayKumar-MSFT
Copy link
Contributor

@geglne, Thanks for the feedback! We are currently investigating and will update you shortly.

@AjayKumar-MSFT
Copy link
Contributor

@geglne, Apologies for the delay! We are checking on this issue further and I have also shared your feedback with the content owner for further review on this topic.

@ctooley21
Copy link

can we get an update here?

@AjayKumar-MSFT
Copy link
Contributor

@ccompy, Requesting your comments on this topic.

@ccompy
Copy link
Contributor

ccompy commented Jun 26, 2019

There are ongoing investments that will make ASE creation much faster. There is nothing further to report on a public website around that activity other than it is ongoing. I will have a lot more to say on the subject at Ignite.

@AjayKumar-MSFT
Copy link
Contributor

The status code issue is being fixed with our next deployment however we do not have an ETA to share yet. Thank you for your patience and co-operation!

@PRMerger7 PRMerger7 added the Pri1 label Sep 9, 2019
@AjayKumar-MSFT
Copy link
Contributor

We will close this out, but if you feel you need more information please just let us know.

@seancunningham
Copy link

It has been over a year now on this and the problem seems to persist. Are there any updates on fixing this functionality?

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

6 participants