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

[BUG] Azure.Security.KeyVault.Secrets preview2 uses 1970 to populate the Created and Updated properties #7197

Closed
3 tasks done
KSchlobohm opened this issue Aug 7, 2019 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault

Comments

@KSchlobohm
Copy link

KSchlobohm commented Aug 7, 2019

Describe the bug
When creating a new Secret the new value is stored as 1/19/1970 rather than current DateTime and the properties for Created and Updated on the Secret object are read-only.

Exception or Stack Trace
N\A

To Reproduce

  1. Create a Secret

Code Snippet

            SecretClient client = new SecretClient(
                vaultUri: new Uri("https://ux-bash-keyvault.vault.azure.net/"),
                credential: new DefaultAzureCredential());

            Secret newSecret = new Secret("newSecret", "createdToday");
            Secret newSecretResponse = client.Set(newSecret);
            Console.WriteLine("newSecret Created: " + newSecretResponse.Created);
            Console.WriteLine("newSecret Updated: " + newSecretResponse.Updated);

Expected behavior

  • Expected to be able to set these values or have the values set during the life-cycle of saving the data when they're set to read-only.

Screenshots
Created and Updated dates not set

Setup (please complete the following information):

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

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
@triage-new-issues triage-new-issues bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 7, 2019
@loarabia loarabia added Client This issue points to a problem in the data-plane of the library. KeyVault labels Aug 7, 2019
@triage-new-issues triage-new-issues bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 7, 2019
@KSchlobohm
Copy link
Author

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

@AlexGhiondea
Copy link
Contributor

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

@heaths heaths assigned heaths and unassigned schaabs Aug 27, 2019
heaths added a commit to heaths/azure-sdk-for-net that referenced this issue Aug 28, 2019
heaths added a commit that referenced this issue Aug 28, 2019
@heaths heaths closed this as completed Aug 28, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Projects
None yet
Development

No branches or pull requests

5 participants