Skip to content

Minor fixes to toward move to GA#153

Merged
tsubasaxZZZ merged 11 commits intoAzure:mainfrom
tsubasaxZZZ:tsunomur-fix-1221
Jan 17, 2024
Merged

Minor fixes to toward move to GA#153
tsubasaxZZZ merged 11 commits intoAzure:mainfrom
tsubasaxZZZ:tsunomur-fix-1221

Conversation

@tsubasaxZZZ
Copy link
Contributor

@tsubasaxZZZ tsubasaxZZZ commented Dec 27, 2023

@tsubasaxZZZ tsubasaxZZZ self-assigned this Dec 27, 2023
@tsubasaxZZZ tsubasaxZZZ changed the title Minor fix for forward moving GA Minor fixes to toward move to GA Dec 27, 2023
@tsubasaxZZZ tsubasaxZZZ marked this pull request as ready for review December 29, 2023 04:53
"storage_workbook_resource_id" = azurerm_application_insights_workbook.storage[0].id
"web_workbook_resource_id" = azurerm_application_insights_workbook.web[0].id
"servicealert_workbook_resource_id" = azurerm_application_insights_workbook.servicealert[0].id
"resiliencyscenarios_workbook_resource_id" = azurerm_application_insights_workbook.resiliencyscenarios[0].id
Copy link
Contributor

@infosatheesh2020 infosatheesh2020 Jan 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is better to rename this to something similar to "resiliencyscenario_crossregion" or "crrResiliencyScenario" because there might be new workbooks supporting other resiliency scenarios in future. Feel free to use your own name but should be able to include additional resiliency scenarios without renaming this workbook name.

(type == 'microsoft.web/serverfarms'), iff(properties.zoneRedundant == 'true', 'Configured', 'Not Configured'),
(type == 'microsoft.sql/servers/databases' and sku.tier <> 'DataWarehouse'), case( //SQL AZ SKU & region availability filter
sku.name == 'Basic' or sku.name == 'Standard' or sku.name == 'System', 'Not Applicable',
sku.name == 'GeneralPurpose' and location !in~ ('westeurope', 'northeurope', 'westus2', 'francecentral', 'eastus', 'eastus2', 'southeastasia', 'qatarcentral', 'australiaeast', 'japaneast', 'uksouth'), 'Not Applicable',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to ensure whether we validate the regions supported for GP tier: https://learn.microsoft.com/en-us/azure/reliability/migrate-sql-database?tabs=portal#prerequisites

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated about this in this commit.
ac51f7b

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename the variables, file names, etc. to make it specific to cross region scenario. There might be new scenarios in the future, so we need to make it modularize and extensible without touching this file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If a new scenario is created under 'Resiliency scenario', a glue template is created as in the other tabs, which remains flexible.
Therefore, the meaning of "resiliencyscenario" in this commit will remain the same, even if additional workbooks are added under it in the future.

"storage_workbook_resource_id" = "community-Workbooks/Azure Advisor/Reliability/Storage"
"web_workbook_resource_id" = "community-Workbooks/Azure Advisor/Reliability/Web"
"servicealert_workbook_resource_id" = "community-Workbooks/Azure Advisor/Reliability/ServiceAlert"
"resiliencyscenarios_workbook_resource_id" = "community-Workbooks/Azure Advisor/Reliability/ResiliencyScenarios"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename required

Copy link
Contributor

@infosatheesh2020 infosatheesh2020 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the environment folder is mainly to create the test data for the workbook, can we exclude it from the repo (part of .gitignore)?

or at least make it clear that it is for test env and by default it skips the creation and can be enabled with a flag value set.

@tsubasaxZZZ tsubasaxZZZ merged commit 67a6bcb into Azure:main Jan 17, 2024
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

Successfully merging this pull request may close these issues.

Number of instances status for App Service Plan is incorrect Update zone list

2 participants