[BUG] Azure.Security.KeyVault.Secrets preview2 doesn't support update

[KSchlobohm]

Describe the bug
Following along with the documentation the process for updating a secret is shown. This process does not compile (the Secret constructor requires 2 string params) and does not succeed due to a required parameter of secret.Version which is a read-only property.

NOTE: another issue with the example is that the returned object from client.Update is of type SecretBase which does not have a "Value" property as shown in the example. This "missing property" issue also applies to the delete example in the Readme.md file.

Exception or Stack Trace

• System.ArgumentNullException: 'Value cannot be null. (Parameter 'secret.Version')'

To Reproduce
Steps to reproduce the behavior:

1. Example

Code Snippet

Secret secret = new Secret("secret-name");

// Clients may specify the content type of a secret to assist in interpreting the secret data when it's retrieved
secret.ContentType = "text/plain";

// You can specify additional application-specific metadata in the form of tags.
secret.Tags["foo"] = "updated tag";

SecretBase updatedSecret = client.Update(secret);

Console.WriteLine(updatedSecret.Name);
Console.WriteLine(updatedSecret.Value);
Console.WriteLine(updatedSecret.Version);
Console.WriteLine(updatedSecret.ContentType);

Expected behavior
Expecting to be able to set the version of the secret and receive an updatedSecret response.

Screenshots
If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

• OS: [Windows 10]
• IDE : [Visual Studio]
• Version of the Library used: Azure.Security.KeyVault.Secrets -Version 4.0.0-preview.2

Additional context
Add any other context about the problem here.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[KSchlobohm]

Looks like the link to the KeyVault Readme is changing with regard to the link for Steps to Reproduce.

[AlexGhiondea]

@KSchlobohm thanks for pointing this out! We'll take a look at this!

[heaths]

Thanks for the feedback! The server API actually only updates secret attributes, so the value isn't part of the response, though if required to be passed in could simply be cached. We are considering what this API will look like and how it relates to the other bug about GetSecrets() returning a SecretBase. As such, we'll consider this for preview 4.

[heaths]

The client code was fixed in #7729. Will leave open to track making sure the samples are updated.