Skip to content

Guest Configuration: Update SDK version to 2024-04-05#30642

Merged
sreallymatt merged 2 commits intohashicorp:mainfrom
cloudk1d:jn/guest-configuration-api-update
Oct 3, 2025
Merged

Guest Configuration: Update SDK version to 2024-04-05#30642
sreallymatt merged 2 commits intohashicorp:mainfrom
cloudk1d:jn/guest-configuration-api-update

Conversation

@cloudk1d
Copy link
Contributor

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

Update the SDK version for guestconfiguration to API version 2024-04-05.

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)

Change Log

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

  • azurerm_resource - support for the thing1 property [GH-00000]

This is a (please select all that apply):

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

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the provider.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Note

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

Copy link
Collaborator

@sreallymatt sreallymatt left a comment

Choose a reason for hiding this comment

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

Hi @terminalPoltergeist, could you rebase this on main to resolve the conflicts? Once that's done I'll kick off the tests for these changes

@cloudk1d cloudk1d force-pushed the jn/guest-configuration-api-update branch from 5b5d5bd to 420d80d Compare October 2, 2025 20:31
Copy link
Collaborator

@sreallymatt sreallymatt left a comment

Choose a reason for hiding this comment

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

Thanks @terminalPoltergeist LGTM 🚢

Test results:
image

@sreallymatt sreallymatt merged commit efd01c5 into hashicorp:main Oct 3, 2025
33 checks passed
@github-actions github-actions bot added this to the v4.48.0 milestone Oct 3, 2025
@cloudk1d cloudk1d deleted the jn/guest-configuration-api-update branch October 3, 2025 19:32
@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

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 Nov 3, 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