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

d/azurerm_recovery_services_vault: expose identity property #26254

Merged
merged 9 commits into from
Aug 14, 2024

Conversation

jkroepke
Copy link
Contributor

@jkroepke jkroepke commented Jun 6, 2024

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

We would like to know the identity of an recovery vault via data source.

I was super uncomfortable with the untyped data source and I migrate the data source to an typed one.

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)
=== RUN   TestAccDataSourceAzureRMRecoveryServicesVault_basic
=== PAUSE TestAccDataSourceAzureRMRecoveryServicesVault_basic
=== CONT  TestAccDataSourceAzureRMRecoveryServicesVault_basic
--- PASS: TestAccDataSourceAzureRMRecoveryServicesVault_basic (168.89s)
=== RUN   TestAccDataSourceAzureRMRecoveryServicesVault_basicWithIdentity
=== PAUSE TestAccDataSourceAzureRMRecoveryServicesVault_basicWithIdentity
=== CONT  TestAccDataSourceAzureRMRecoveryServicesVault_basicWithIdentity
--- PASS: TestAccDataSourceAzureRMRecoveryServicesVault_basicWithIdentity (228.48s)
PASS

Change Log

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

  • azurerm_recovery_services_vault - expose identity property on data source [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

Related Issue(s)

Fixes #0000

Note

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

@jkroepke jkroepke force-pushed the data-source-recovery-vault branch from 9951fef to 8f52464 Compare June 6, 2024 10:17
@jkroepke jkroepke marked this pull request as ready for review June 6, 2024 10:25
@jkroepke jkroepke changed the title d/azurerm_recovery_services_vault: expose identity d/azurerm_recovery_services_vault: expose identity property Jun 6, 2024
Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

Thanks for this PR @jkroepke. Could you take a look at the suggestions left in-line? Just a few minor things around consistency and spelling. Once those are fixed up I can kick off the tests.

jkroepke and others added 2 commits August 14, 2024 11:12
…a_source.go

Co-authored-by: stephybun <steph@hashicorp.com>
…a_source.go

Co-authored-by: stephybun <steph@hashicorp.com>
…a_source.go

Co-authored-by: stephybun <steph@hashicorp.com>
Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

Thanks @jkroepke. Tests are running, I think you may have pushed a change that isn't supposed to be in this PR? I left a comment on it. Once that's resolved this should be good to go!

@jkroepke jkroepke force-pushed the data-source-recovery-vault branch from b349c6b to 775134f Compare August 14, 2024 11:44
Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

No worries @jkroepke! Thanks for converting this to a typed data source, it's much appreciated 🙂. Tests are passing, LGTM 🍰

@stephybun stephybun merged commit 1b6e07f into hashicorp:main Aug 14, 2024
34 checks passed
@github-actions github-actions bot added this to the v3.116.0 milestone Aug 14, 2024
stephybun added a commit that referenced this pull request Aug 15, 2024
Copy link

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 Sep 14, 2024
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