azurerm_postgresql_flexible_server - fix sku_name validation function#31538
Draft
v-yhyeo0202 wants to merge 1 commit intohashicorp:mainfrom
Draft
azurerm_postgresql_flexible_server - fix sku_name validation function#31538v-yhyeo0202 wants to merge 1 commit intohashicorp:mainfrom
azurerm_postgresql_flexible_server - fix sku_name validation function#31538v-yhyeo0202 wants to merge 1 commit intohashicorp:mainfrom
Conversation
Contributor
|
This draft pull request is being closed because it has been inactive for 60 days ⏳. This helps our maintainers find and focus on the active contributions. If you would like to continue working on this, please reopen the pull request and mark it as ready for review when complete. Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Community Note
Description
azurerm_postgresql_flexible_serverfails with the following error whensku_namesuch asGP_Standard_D2ds_v6is used. The error is due to the absence of the options from validation function. To fix the issue, the absent options are added to validation function.PR Checklist
I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.For example: “
resource_name_here- description of change e.g. adding propertynew_property_name_here”Changes to existing Resource / Data Source
I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).I have written new tests for my resource or datasource changes & updated any relevant documentation.(For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.Testing
https://hashicorp.teamcity.com/buildConfiguration/TF_AzureRM_AZURERM_SERVICE_PUBLIC_POSTGRES/590429?buildTab=overview



The failed tests are pre-existing from main branch as shown in the log below.
https://hashicorp.teamcity.com/buildConfiguration/TF_AzureRM_AZURERM_SERVICE_PUBLIC_POSTGRES/589663?buildTab=overview
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_postgresql_flexible_server- add absentsku_nameoption in validation functionThis is a (please select all that apply):
Related Issue(s)
Fixes #31518
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the provider.
Note
If this PR changes meaningfully during the course of review please update the title and description as required.