Skip to content

Regenerate confidential ledger from typespec #41924

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

Draft
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

catalinaperalta
Copy link
Member

@catalinaperalta catalinaperalta commented Jul 7, 2025

Regenerate and update the Confidential Ledger library based on the newly migrated typespec project.

Copy link

github-actions bot commented Jul 7, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

azure-confidentialledger

*,
collection_id: Optional[str] = None,
**kwargs: Any,
) -> LROPoller[JSON]:
) -> LROPoller[_models.TransactionStatus]:
Copy link
Member Author

@catalinaperalta catalinaperalta Jul 29, 2025

Choose a reason for hiding this comment

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

If this signature hasnt been shipped as stable, it needs some attention, the true return type here should be LROPoller[LedgerEntry] however due to the underlying usage of the begin_wait_for_commit() method the poller seems to return transactionstatus instead

@catalinaperalta catalinaperalta changed the title [wip] Regen confidential ledger Regenerate confidential ledger from typespec Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants