[YES] Have you followed the guidelines in our Contributing document?
[YES] Have you added an explanation of what your changes do and why you'd like us to include them?
[YES] I have updated the documentation accordingly.
[NA] I have added tests to cover my changes.
[NA] All new and existing tests passed.
[YES] My code follows the code style of this project.
[YES] I ran lint checks locally prior to submission.
[YES] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
What is the current behavior?
The current azurerm provider version (1.4) will not work for new features introduced by > 2.0.0 and to be able to contribute back specific modules such as azure ML workspace, we needed to pump the azurerm provider version to >= 2.6
We had to go with version 2.9 as it has fix for app gateway issues.
Issue Number: N/A
What is the new behavior?
Update provider module
Update backend files for templates
Update keyvault module
Update app-service module
Does this introduce a breaking change?
[YES]
Had to update keyvault module by using "data.azurerm_client_config.current.object_id" instead of "data.azurerm_client_config.current.service_principal_object_id"
Had to remove "virtual_network_name" from app-service module
helayoty
commented
4 years ago
All Submissions:
What is the current behavior?
The current azurerm provider version (1.4) will not work for new features introduced by > 2.0.0 and to be able to contribute back specific modules such as azure ML workspace, we needed to pump the azurerm provider version to >= 2.6
We had to go with version 2.9 as it has fix for app gateway issues.
Issue Number: N/A
What is the new behavior?
Does this introduce a breaking change?
Any relevant logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information