Skip to content

New data source azuread_authentication_strength_policy - #1887

Open
anurag-hashicorp wants to merge 5 commits into
mainfrom
f-authentication-strength-policy-datasource
Open

New data source azuread_authentication_strength_policy#1887
anurag-hashicorp wants to merge 5 commits into
mainfrom
f-authentication-strength-policy-datasource

Conversation

@anurag-hashicorp

@anurag-hashicorp anurag-hashicorp commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Depends on #1881.

This PR should wait for #1881 to merge first and incorporate the schema changes in the Read() so that both the data source and resource are in sync.

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

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/TerraformProviders_AzureAD_AZUREAD_SERVICE_PUBLIC_POLICIES/704726?buildTab=tests

Change Log

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

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 #1385

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.

@jackofallops jackofallops left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks @anurag-hashicorp - One small thing to take a look at, but otherwise looking good.

Comment thread internal/services/policies/authentication_strength_policy_data_source.go Outdated
…list to avoid missing results

Addresses review feedback: ListAuthenticationStrengthPolicies only returns
the first page of results, so lookups by display_name could silently miss
matches beyond the first page.

@jackofallops jackofallops left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Hi @anurag-hashicorp - Sorry, I missed a schema problem in the last pass, should be good to merge after that's changed.

Comment thread internal/services/policies/authentication_strength_policy_data_source.go Outdated
@jackofallops

Copy link
Copy Markdown
Member

@anurag-hashicorp - One more thing, do we need to hold this back behind #1881 - so it can have the additional schema items from that PR added here?

…or allowed_combinations

Computed-only attributes should use TypeList rather than TypeSet, per
review feedback.
@anurag-hashicorp

Copy link
Copy Markdown
Contributor Author

@anurag-hashicorp - One more thing, do we need to hold this back behind #1881 - so it can have the additional schema items from that PR added here?

That's a fair point and I have updated the description. #1881 should merge first and then this data source needs to be updated and merged second.

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.

Add support for "azuread_authentication_strength_policy" data source

3 participants