Skip to content

azurerm_workloads_sap_* - support for the managed_resources_network_access_type property#28881

Merged
mbfrahry merged 1 commit intohashicorp:mainfrom
neil-yechenwei:newfeatureonsapvis
Feb 27, 2025
Merged

azurerm_workloads_sap_* - support for the managed_resources_network_access_type property#28881
mbfrahry merged 1 commit intohashicorp:mainfrom
neil-yechenwei:newfeatureonsapvis

Conversation

@neil-yechenwei
Copy link
Contributor

@neil-yechenwei neil-yechenwei commented Feb 26, 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 support new feature "managedResourcesNetworkAccessType".

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)

--- PASS: TestAccWorkloadsSAPSingleNodeVirtualInstance_basic (2055.50s)
--- PASS: TestAccWorkloadsSAPSingleNodeVirtualInstance_requiresImport (2227.49s)
--- PASS: TestAccWorkloadsSAPSingleNodeVirtualInstance_complete (2173.28s)
--- PASS: TestAccWorkloadsSAPSingleNodeVirtualInstance_update (2959.14s)
--- PASS: TestAccWorkloadsSAPThreeTierVirtualInstance_basic (2882.43s)
--- PASS: TestAccWorkloadsSAPThreeTierVirtualInstance_requiresImport (2915.06s)
--- PASS: TestAccWorkloadsSAPThreeTierVirtualInstance_complete (2951.19s)
--- PASS: TestAccWorkloadsSAPThreeTierVirtualInstance_update (3566.87s)
--- PASS: TestAccWorkloadsSAPDiscoveryVirtualInstanceSequential/sapVirtualInstance/basic (982.93s)
--- PASS: TestAccWorkloadsSAPDiscoveryVirtualInstanceSequential/sapVirtualInstance/requiresImport (1067.22s)
--- PASS: TestAccWorkloadsSAPDiscoveryVirtualInstanceSequential/sapVirtualInstance/complete (1730.71s)
--- PASS: TestAccWorkloadsSAPDiscoveryVirtualInstanceSequential/sapVirtualInstance/update (1875.86s)

Change Log

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

  • azurerm_workloads_sap_* - support for the managed_resources_network_access_type property

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 requested a review from a team as a code owner February 26, 2025 06:51
@neil-yechenwei neil-yechenwei marked this pull request as draft February 26, 2025 06:51
@neil-yechenwei neil-yechenwei marked this pull request as ready for review February 27, 2025 07:56
Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for this @neil-yechenwei!

@mbfrahry mbfrahry added this to the v4.22.0 milestone Feb 27, 2025
@mbfrahry mbfrahry merged commit 09aad13 into hashicorp:main Feb 27, 2025
47 checks passed
mbfrahry added a commit that referenced this pull request Feb 27, 2025
jackofallops added a commit that referenced this pull request Mar 7, 2025
* Update CHANGELOG.md #28843

* Update CHANGELOG.md for #28748

* Update CHANGELOG.md for #28881

* Update CHANGELOG.md for #28909

* Update CHANGELOG.md fold in patch release and expand starred entry correctly

* Update CHANGELOG.md remove duplicate entry for 28843

* Update CHANGELOG.md #28066

* Update CHANGELOG.md for #28902 and fix ordering

* Update CHANGELOG.md for #28848

* Update CHANGELOG.md #27622

* Update CHANGELOG.md for #28271

* Update CHANGELOG.md update format

* Update CHANGELOG.md #28934

* Update for #28619 #28598

* Update CHANGELOG.md #28940

* Update CHANGELOG.md for #28880

* Update CHANGELOG.md for #28617

* Update CHANGELOG.md #28721

* Update CHANGELOG.md #28949

* Update previous entry for 4.16.0

* Update CHANGELOG.md for #28834

* prep for release

---------

Co-authored-by: Matthew Frahry <mbfrahry@gmail.com>
Co-authored-by: jackofallops <11830746+jackofallops@users.noreply.github.com>
Co-authored-by: catriona-m <86247157+catriona-m@users.noreply.github.com>
Co-authored-by: stephybun <steph@hashicorp.com>
Co-authored-by: Wodans Son <20408400+WodansSon@users.noreply.github.com>
Co-authored-by: jackofallops <ste@hashicorp.com>
@github-actions
Copy link
Contributor

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants