You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The MS SQL database db_permissions execution fails in non Azure Public clouds. This is because the URI suffix is hard coded into the module and is different for each cloud.
By passing the cloud information automatically down as a global setting, module authors are able to customize the behavior of their module for individual clouds when needed by using the proper variable instead of a string value.
The goal of this story is enhance sovereign cloud support by passing this value to CAF landing zones and modules as global settings. This allows modules and add-ons to conditionally load different configurations for different clouds.
The update consists of 3 repo updates:
Rover retrieval of cloud variables and setting them to environment variables
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Error on or near line 286: Error running terraform apply; exiting with status 2001\
Expected behavior
The terraform deployment and db permission scripts should have the proper suffix and therefore connect and apply the permissions as required.
Configuration (please complete the following information):
Rover devcontainer latest
Landing zones latest
Azurerm modules latest
Additional context
Values can be retrieved by running 'az cloud show' in the respective cloud. This is run as part of rover and the values are extracted so they do not have to be set by the user.
The text was updated successfully, but these errors were encountered:
davesee
changed the title
[bug] Add soveregin cloud endpoints and suffixes for modules (step 2)
[bug] Add soveregin cloud endpoints and suffixes for modules (part 2)
May 20, 2021
Describe the bug
The MS SQL database db_permissions execution fails in non Azure Public clouds. This is because the URI suffix is hard coded into the module and is different for each cloud.
By passing the cloud information automatically down as a global setting, module authors are able to customize the behavior of their module for individual clouds when needed by using the proper variable instead of a string value.
The goal of this story is enhance sovereign cloud support by passing this value to CAF landing zones and modules as global settings. This allows modules and add-ons to conditionally load different configurations for different clouds.
The update consists of 3 repo updates:
To Reproduce
Steps to reproduce the behavior:
0. Login to a non Azure Public cloud
Expected behavior
The terraform deployment and db permission scripts should have the proper suffix and therefore connect and apply the permissions as required.
Configuration (please complete the following information):
Additional context
Values can be retrieved by running 'az cloud show' in the respective cloud. This is run as part of rover and the values are extracted so they do not have to be set by the user.
The text was updated successfully, but these errors were encountered: