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

Terraform is registering all the providers in Azure subscription and failing sometime #4

Open
sanketnagdive opened this issue Feb 22, 2024 · 2 comments

Comments

@sanketnagdive
Copy link
Collaborator

For new azure subscription we have observed that few providers needs to be register or else script will try to register all the providers/services in Azure which are not required as well. Its best practice to make sure only the required services are registered.
Also, script is failing and giving the following error while registering the providers some times
"Getting error after running ./install.sh ""│ More information on the ""skip_provider_registration"" flag can be found here:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#skip_provider_registration

│ Original Error: Cannot register providers: Microsoft.AVS. Errors were: waiting for Subscription Provider (Subscription: ""d9908e94-6899-4ef6-8a14-5a185b3b7254""
│ Provider Name: ""Microsoft.AVS"") to be registered: context deadline exceeded

│ with provider[""registry.terraform.io/hashicorp/azurerm""],
│ on main.tf line 1, in provider ""azurerm"":
│ 1: provider ""azurerm"" {"

We can instruct the user to make sure the required services/providers are registered and update the terraform scripts to skip the registration of all the services. I have raised PR for the same
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/resource_provider_registration

cc @gandham-santhosh @mohitga @vinukumar-vs @santhosh-tg @keshavprasadms

@mohitga
Copy link

mohitga commented Feb 23, 2024

Thanks @sanketnagdive
@keshavprasadms can you look at it once?

@beepdot
Copy link
Contributor

beepdot commented Feb 26, 2024

We used the Azure account provided by the sunbird team. We don't have access to any other azure account to replicate this issue. It worked without any issues in the account provided by the Sunbird team. If the team has identified some issues, its good to add that in the README document. As we wont know what would be the configurations of a customer's Azure account and it can have many permissions / restrictions, it better to address this in documentation and add more contents in the docs as and when a customer encounters other such Azure acocunt issues.

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

No branches or pull requests

3 participants