Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Postgresql Admin/Database/FirewallRule/VirtualEndpoint API version from 2023-06-01-preview/2022-12-01 to 2024-08-01 #28474

Merged

Conversation

neil-yechenwei
Copy link
Contributor

@neil-yechenwei neil-yechenwei commented Jan 10, 2025

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

Service team asks us to upgrade Postgresql Admin/Database/FirewallRule/VirtualEndpoint API version to 2024-08-01

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 relevent 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)

image

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

  • Upgrade Postgresql Admin/Database/FirewallRule/VirtualEndpoint API version from 2023-06-01-preview/2022-12-01 to 2024-08-01

This is a (please select all that apply):

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

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

@neil-yechenwei neil-yechenwei changed the title Upgrade Postgresql API version from 2023-06-01-preview/2022-12-01 to 2024-08-01 Upgrade Postgresql Admin/Database/FirewallRule/VirtualEndpoint API version from 2023-06-01-preview/2022-12-01 to 2024-08-01 Jan 10, 2025
@neil-yechenwei neil-yechenwei marked this pull request as ready for review January 10, 2025 13:05
Copy link
Member

@jackofallops jackofallops left a comment

Choose a reason for hiding this comment

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

Thanks @neil-yechenwei - LGTM 👍

@jackofallops jackofallops merged commit 185503e into hashicorp:main Jan 15, 2025
33 checks passed
@github-actions github-actions bot added this to the v4.16.0 milestone Jan 15, 2025
jackofallops added a commit that referenced this pull request Jan 15, 2025
jackofallops added a commit that referenced this pull request Jan 16, 2025
* update for #27680

* Update CHANGELOG.md for #28465

* Update CHANGELOG.md #27932

* Update CHANGELOG.md for #28505

* Update CHANGELOG.md for #28474

* Update CHANGELOG.md #28516

* Update CHANGELOG for #28456

* Update CHANGELOG.md for #28472

* Update CHANGELOG.md #28307

* Update CHANGELOG.md for #27859

* Update for #28519

* Update for #27791 #27528

* Update CHANGELOG.md for #28527

* update changelog links and generate provider schema

---------

Co-authored-by: jackofallops <[email protected]>
Co-authored-by: catriona-m <[email protected]>
Co-authored-by: sreallymatt <[email protected]>
Co-authored-by: Matthew Frahry <[email protected]>
Co-authored-by: jackofallops <[email protected]>
NotTheEvilOne pushed a commit to b1-systems/terraform-provider-azurerm that referenced this pull request Jan 20, 2025
…corp#28474)

* Upgrade Postgresql API version from 2023-06-01-preview to 2024-08-01

* remove postgresql fs

* revert postgresql fs
NotTheEvilOne pushed a commit to b1-systems/terraform-provider-azurerm that referenced this pull request Jan 20, 2025
* update for hashicorp#27680

* Update CHANGELOG.md for hashicorp#28465

* Update CHANGELOG.md hashicorp#27932

* Update CHANGELOG.md for hashicorp#28505

* Update CHANGELOG.md for hashicorp#28474

* Update CHANGELOG.md hashicorp#28516

* Update CHANGELOG for hashicorp#28456

* Update CHANGELOG.md for hashicorp#28472

* Update CHANGELOG.md hashicorp#28307

* Update CHANGELOG.md for hashicorp#27859

* Update for hashicorp#28519

* Update for hashicorp#27791 hashicorp#27528

* Update CHANGELOG.md for hashicorp#28527

* update changelog links and generate provider schema

---------

Co-authored-by: jackofallops <[email protected]>
Co-authored-by: catriona-m <[email protected]>
Co-authored-by: sreallymatt <[email protected]>
Co-authored-by: Matthew Frahry <[email protected]>
Co-authored-by: jackofallops <[email protected]>
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.

2 participants