Fix Status and StatusMessage fields in Get-AzSqlDatabaseImportExportStatus to conform to documentation #13751
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
#12899 introduced a bug which caused the Status and StatusMessage fields of the Get-AzSqlDatabaseImportExportStatus calls to be wrong:
This does not line up with our documentation and was causing significant confusion.
For instance, in our documentation, we have:
However, with releases after 2.10.0, we would actually return
I have re-activated some tests which were removed in the previous PR, though most of the test seems to be hitting an SDK issue (see in-code comments). I have opened a work item on the Import/Export service team's backlog to address this SDK issue.
Checklist
CONTRIBUTING.mdChangeLog.mdfile(s) has been updated:ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md## Upcoming Releaseheader -- no new version header should be added