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

Add api key whitelist hot reloading and small touch-up #458

Merged
merged 7 commits into from
Apr 4, 2024

Conversation

yuroitaki
Copy link
Member

This PR mainly adds hot reloading capability of api key whitelist, i.e. modification of the whitelist file will be automatically applied without needing to restart the server.

There are also some small touchups on the code

  • Make static html returned from root endpoint configurable by notary server operator
  • Remove prover ip from logging

Copy link
Member

@heeckhau heeckhau left a comment

Choose a reason for hiding this comment

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

Looks good to me

Copy link
Member

@sinui0 sinui0 left a comment

Choose a reason for hiding this comment

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

lgtm, other than the async mutex

notary-server/src/server.rs Outdated Show resolved Hide resolved
@yuroitaki yuroitaki requested a review from sinui0 April 3, 2024 12:18
@yuroitaki yuroitaki merged commit 5c0a030 into dev Apr 4, 2024
15 checks passed
sinui0 pushed a commit that referenced this pull request Apr 9, 2024
* Add hot reload of api key, remove prover ip, move html static text.

* Add documentation.

* Toggle back config, add comments.

* Edit comment and html info.

* Edit comment.

* Change to sync mutex.
sinui0 added a commit that referenced this pull request Apr 9, 2024
@yuroitaki yuroitaki deleted the notary-server/hot-reload-api-key branch May 6, 2024 07:53
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.

3 participants