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

Migrate Key Vault client generation to TypeSpec #31512

Closed
4 tasks
chlowell opened this issue Oct 24, 2024 · 3 comments
Closed
4 tasks

Migrate Key Vault client generation to TypeSpec #31512

chlowell opened this issue Oct 24, 2024 · 3 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Milestone

Comments

@chlowell
Copy link
Member

This issue tracks migrating Key Vault client generation from OpenAPI to TypeSpec:

  • administration
  • certificates
  • keys
  • secrets

This is the high-level process for each library:

@chlowell chlowell added Client This issue points to a problem in the data-plane of the library. KeyVault labels Oct 24, 2024
@chlowell chlowell added this to the 2024-11 milestone Oct 24, 2024
@chlowell chlowell moved this from Untriaged to Not Started in Azure SDK for Key Vault Oct 24, 2024
@chlowell chlowell modified the milestones: 2024-11, 2024-12 Nov 14, 2024
@maorleger
Copy link
Member

@maorleger maorleger moved this from Not Started to In Progress in Azure SDK for Key Vault Nov 14, 2024
@maorleger
Copy link
Member

I got PRs ready for all 4 packages:

Needed a bunch of workarounds which I am tracking issues for and will work on soon as this is merged, but right now I am just waiting for the typespec files to be merged for me to wrap these up

@maorleger maorleger modified the milestones: 2024-12, 2025-01 Dec 10, 2024
@maorleger maorleger modified the milestones: 2025-01, 2025-02 Jan 6, 2025
maorleger added a commit that referenced this issue Jan 16, 2025
### Packages impacted by this PR

@azure/keyvault-admin

### Issues associated with this PR

#31512

Generates client using TypeSpec, with any workarounds scripted and noted
maorleger added a commit that referenced this issue Jan 17, 2025
### Packages impacted by this PR

@azure/keyvault-certificates

### Issues associated with this PR

#31512

### Describe the problem that is addressed by this PR

Migrates keyvault-certificates to TypeSpec
maorleger added a commit that referenced this issue Jan 21, 2025
### Packages impacted by this PR

@azure/keyvault-keys

### Issues associated with this PR

#31512

### Describe the problem that is addressed by this PR

Generates client using TypeSpec, with any workarounds scripted and noted
maorleger added a commit that referenced this issue Jan 21, 2025
### Packages impacted by this PR

@azure/keyvault-secrets

### Issues associated with this PR

#31512

### Describe the problem that is addressed by this PR

Migrates keyvault-secrets to TypeSpec
@maorleger
Copy link
Member

Completed via the above linked PRs 🥳

@github-project-automation github-project-automation bot moved this from In Progress to Done in Azure SDK for Key Vault Jan 21, 2025
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
Status: Done
Development

No branches or pull requests

2 participants