Update azure-confidentialeledger SDK with latest TypeSpec definitions #41087
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.
Azure Confidential Ledger SDK Update
Summary of Changes
This PR updates the azure-confidentialeledger SDK with the latest TypeSpec definitions from the local azure-rest-api-specs repository. The update was performed by initializing the SDK from the local TypeSpec configuration.
Key Updates:
Validation Results
The following validation checks were performed on the updated SDK:
Additional Notes
This update ensures the azure-confidentialeledger SDK remains aligned with the latest API specifications and follows the Azure SDK Python design guidelines.