Conversation
…ckages younger than 7 days
…ckages younger than 7 days
Svenum
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR introduces the Basic routes for these features:
All of these routes live under the prefix /api/v1/iglu/rest .
Anything that has to do with the Tenants (Tenants, Derivations, Access Rules) are hosted under /api/v1/iglu/rest/tenants and anything else is hosted under /api/v1/iglu/rest/keys.
These Reset Routes need to be enabled by setting enable_rest = true in the server section of your config.toml. This is done so that public facing instances won't have to expose these functions if you the Administrator does not want to do that.
I plan to support only specific IPs for the Rest routes in the future (i.e you can only whitelist the controller IP once we actually get that thing going).