we renamed the file but did not update the baseline file. Fix it.

[xiangyan99]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[xiangyan99]

/azp run python - hdinsight - ci

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[mccoyp]

CI run for this PR: https://dev.azure.com/azure-sdk/public/_build/results?buildId=1524529&view=results

[mccoyp]

Looks like the warning is still being raised despite the name update in the baseline file. @sima-zhu, do you know why that is?

@xiangyan99 if the package owners are okay with us making a change on their behalf, could we move the fake secret that's raising the error into our fake credential store instead, and import it in the test file? We could then remove the baseline suppression entirely, which is the eventual goal anyway. We could probably name the secret value MGMT_HDINSIGHT_FAKE_KEY

[xiangyan99]

Looks like the warning is still being raised despite the name update in the baseline file. @sima-zhu, do you know why that is?

@xiangyan99 if the package owners are okay with us making a change on their behalf, could we move the fake secret that's raising the error into our fake credential store instead, and import it in the test file? We could then remove the baseline suppression entirely, which is the eventual goal anyway. We could probably name the secret value MGMT_HDINSIGHT_FAKE_KEY

I am ok to move it into our fake cred store. But we still want to know why it failed? @sima-zhu

[sima-zhu]

Looks like the warning is still being raised despite the name update in the baseline file. @sima-zhu, do you know why that is?
@xiangyan99 if the package owners are okay with us making a change on their behalf, could we move the fake secret that's raising the error into our fake credential store instead, and import it in the test file? We could then remove the baseline suppression entirely, which is the eventual goal anyway. We could probably name the secret value MGMT_HDINSIGHT_FAKE_KEY

I am ok to move it into our fake cred store. But we still want to know why it failed? @sima-zhu

Right, the baseline file is using hash somehow. Rename directly does not fix the error.

[sima-zhu]

Python has guideline of fixing this. It is better to fix as @mccoyp suggested.

[xiangyan99]

@mccoyp could you help to move those fake secrets into our fake credential store?

[xiangyan99]

Close this one as we will use #24274 instead.