Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Administration backup LROs to conform to guidelines #17440

Merged
merged 8 commits into from
Jan 5, 2021

Conversation

christothes
Copy link
Member

closes #17381

@ghost ghost added the KeyVault label Dec 9, 2020
@christothes christothes self-assigned this Dec 9, 2020
@christothes christothes added the Client This issue points to a problem in the data-plane of the library. label Dec 9, 2020
Copy link
Contributor

@chamons chamons left a comment

Choose a reason for hiding this comment

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

Really dumb question - Keyvault is a shipped service, right?

How is changing public properties names:

    public System.Collections.Generic.IList<string> AllowedActions { get { throw null; } }
    public System.Collections.Generic.IList<string> AllowedDataActions { get { throw null; } }
    public System.Collections.Generic.IList<string> DeniedActions { get { throw null; } }
    public System.Collections.Generic.IList<string> DeniedDataActions { get { throw null; } }

not an API break?

@heaths
Copy link
Member

heaths commented Jan 5, 2021

@chamons , the service shipped, but the SDK with these members hasn't GA'd. We don't always use the same names for a better UX, and that is the case here.

}
if (_value != null && _value.EndTime.HasValue && _value.Error != null)
{
_requestFailedException = new RequestFailedException($"{_value.Error.Message}\nInnerError: {_value.Error.InnerError}\nCode: {_value.Error.Code}");
Copy link
Member

Choose a reason for hiding this comment

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

Do we not already have a utility method in Core, perhaps, that would do this consistently?

Copy link
Member Author

Choose a reason for hiding this comment

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

Which part were you thinking should be consistent? The error payload in this case is specific to the service.

Copy link
Member

Choose a reason for hiding this comment

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

The formatting itself.

@@ -37,6 +37,7 @@ public async Task ResumeBackupRestore()

// Construct a BackupOperation using a KeyVaultBackupClient and the Id from a previously started operation.
BackupOperation backupOperation = new BackupOperation(client, backupOperationId);
/*@@*/backupOperation._retryAfterSeconds = (int)PollingInterval.TotalSeconds;
Copy link
Member

Choose a reason for hiding this comment

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

👍

@christothes christothes merged commit 1a95f19 into Azure:master Jan 5, 2021
annelo-msft pushed a commit to annelo-msft/azure-sdk-for-net that referenced this pull request Feb 17, 2021
* fixup LROs to conform to guidelines, add tests
@christothes christothes deleted the users/chriss/LROGuidelines branch October 27, 2021 19:10
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this pull request Jan 21, 2022
[Go] Rename stuttering (Azure#17440)

* [Go] rename stuttering

* fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Key Vault Administration LROs should conform to updated guidelines
3 participants