azurerm_mongo_cluster - remove the check logic for administrator_password

[neil-yechenwei]

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

When running tf apply, the logic in CustomizeDiff checks if the AdministratorPassword is empty, but at that point, random_password has not yet generated the value, so the check fails. To fix this issue, the check for AdministratorPassword can be removed, as the logic for checking AdministratorUsername already exists in CustomizeDiff, and this field has the RequiredWith: []string{"administrator_password"} validation. Therefore, redundant checks in CustomizeDiff are not necessary.

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)

Change Log

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

• azurerm_mongo_cluster - remove the check logic for administrator_password

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

Note

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

[stephybun]

This validation should probably be moved to the Create function instead of removed entirely

[neil-yechenwei]

Even if the validation is placed in the create function, this code will never be hit because administrator_username already has the constraint RequiredWith: []string{"administrator_password"}.

[stephybun]

Thanks for pointing that out 👍

[neil-yechenwei]

@stephybun , thanks for the comments. I left suggestion. Please take another look.

[stephybun]

Thanks @neil-yechenwei LGTM 👍