Skip to content

azurerm_datadog_monitor_sso_configuration deprecate single_sign_on_enabled property#28520

Merged
wyattfry merged 25 commits intomainfrom
wyatt/todos-4-0-datadog-sso-config
Mar 7, 2025
Merged

azurerm_datadog_monitor_sso_configuration deprecate single_sign_on_enabled property#28520
wyattfry merged 25 commits intomainfrom
wyatt/todos-4-0-datadog-sso-config

Conversation

@wyattfry
Copy link
Copy Markdown
Contributor

@wyattfry wyattfry commented Jan 15, 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

  • Deprecates the single_sign_on_enabled property in favor of single_sign_on (a 4.0 TODO)

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)

The unit tests have been skipped for a long time and fixing them is outside the scope of this PR.

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)

Relates to https://github.com/hashicorp/tf-azure-stratosphere/issues/245

Note

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

@wyattfry
Copy link
Copy Markdown
Contributor Author

Unfortunately I have not yet found a Datadog API key, so I can't run the tests yet
image

Copy link
Copy Markdown
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.

Thanks for this @wyattfry. Datadog SSO stuff looks great as does removing the provider test stuff but unfortunately, some of the 4.0 removal stuff can't be done because it currently works in 4.0 and will break people if we remove it the way it's written

Copy link
Copy Markdown
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.

spotted a couple extras to @mbfrahry's review

@wyattfry wyattfry changed the title Resolving 4.0 Resource TODOs Resolving 4.0 TODOs Datadog SSO Jan 16, 2025
@wyattfry wyattfry marked this pull request as ready for review February 19, 2025 14:31
@wyattfry wyattfry requested a review from mbfrahry February 19, 2025 14:31
Copy link
Copy Markdown
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.

Hey @wyattfry, I think these changes look good though I think it would be good to run the tests on this resource, did you figure out a way to do so?

@wyattfry wyattfry requested a review from sreallymatt March 6, 2025 20:09
Copy link
Copy Markdown
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!

Copy link
Copy Markdown
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 @wyattfry, LGTM

@wyattfry wyattfry merged commit a4a6a3d into main Mar 7, 2025
37 checks passed
@wyattfry wyattfry deleted the wyatt/todos-4-0-datadog-sso-config branch March 7, 2025 10:55
@github-actions github-actions bot added this to the v4.23.0 milestone Mar 7, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 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 Apr 7, 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.

5 participants