Skip to content

azurerm_postgresql_flexible_server - fix sku_name validation function#31538

Draft
v-yhyeo0202 wants to merge 1 commit intohashicorp:mainfrom
v-yhyeo0202:fix-issue-31518
Draft

azurerm_postgresql_flexible_server - fix sku_name validation function#31538
v-yhyeo0202 wants to merge 1 commit intohashicorp:mainfrom
v-yhyeo0202:fix-issue-31518

Conversation

@v-yhyeo0202
Copy link
Copy Markdown
Collaborator

@v-yhyeo0202 v-yhyeo0202 commented Jan 20, 2026

Community Note

  • Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

azurerm_postgresql_flexible_server fails with the following error when sku_name such as GP_Standard_D2ds_v6 is 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.

"sku_name" is not a valid sku name, got GP_Standard_D2ds_v6
│ 
│   with module.axso_postgresql_flexible_server.azurerm_postgresql_flexible_server.pgsqlflexible_server,
│   on .terraform/modules/axso_postgresql_flexible_server/main.tf line 61, in resource "azurerm_postgresql_flexible_server" "pgsqlflexible_server":
│   61:   sku_name            = var.sku_name

PR Checklist

  • I have followed the guidelines in our Contributing Documentation.
  • I have checked to ensure there aren't other open Pull Requests for the same update/change.
  • I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
  • 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.
  • I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
    For example: “resource_name_here - description of change e.g. adding property new_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.
  • I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
  • (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

  • My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

https://hashicorp.teamcity.com/buildConfiguration/TF_AzureRM_AZURERM_SERVICE_PUBLIC_POSTGRES/590429?buildTab=overview
image
image
image

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 absent sku_name option in validation function

This is a (please select all that apply):

  • Bug Fix
  • New Feature (ie adding a service, resource, or data source)
  • Enhancement
  • Breaking Change

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.

@github-actions
Copy link
Copy Markdown
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!

@v-yhyeo0202 v-yhyeo0202 reopened this Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GP_Standard_D4ds_v6 for Azure PostgreSQL Flexible server is not a valid sku name

2 participants