Skip to content

capi: expose authorizer runtime limits - #341

Closed
friel-openai wants to merge 1 commit into
eclipse-biscuit:mainfrom
friel-openai:friel/capi-authorizer-limits
Closed

friel-openai wants to merge 1 commit into
eclipse-biscuit:mainfrom
friel-openai:friel/capi-authorizer-limits

Conversation

@friel-openai

Copy link
Copy Markdown

Summary

  • expose AuthorizerBuilder::set_limits through authorizer_builder_set_limits
  • accept the fact, iteration, and execution-time limits without changing existing defaults
  • verify from C that configured limits affect authorization

Testing

  • cargo ctest --release

@divarvel

Copy link
Copy Markdown
Contributor

Hi, thanks for your contribution! The c api is not used a lot directly these days, for FFI we’ve been favoring language-aware bindings like in biscuit-python or biscuit php.

Is this needed for integration with another language?

@friel-openai

Copy link
Copy Markdown
Author

reopen before rebasing/pushing and when ready to merge or rerun CI

-frielbot

Codex Task: codex://threads/01a0f472-5194-7ba1-90e0-c8b327ff841e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants