Repository navigation
Deploy atomic-integration-proxy 0.3.0 - #83
Merged
Merged
Conversation
Bump the pinned crate to 0.3.0 and lock it (adds hmac 0.12). 0.3.0 limits key checks per client network and platform and reads the client address from TRUST_FORWARDED_FOR; localthought.io sets TRUST_FORWARDED_FOR=heroku. The wrapper only calls run(), which uses Config::from_env, so the new Config fields need no code change. Document both new variables in .env.example. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Bumps the wrapper to
atomic-integration-proxy0.3.0 (crates.io, tagintegration-proxy-v0.3.0, ontola/atomic-plugins#341).Cargo.toml:=0.2.5->=0.3.0;Cargo.lockviacargo update -p atomic-integration-proxy(addshmac0.12)..env.example: documents the newTRUST_FORWARDED_FORandKEY_CHECK_LIMIT_PER_HOUR.src/main.rsonly callsrun(), which buildsConfigwithfrom_env, so the two new publicConfigfields don't affect it.0.3.0 limits key checks per client network and platform. On Heroku it needs
TRUST_FORWARDED_FOR=heroku, which is set on the app before this merges, or every client shares the router's rate-limit bucket.Checked locally:
cargo fmt --check,cargo clippy --locked --all-targets -D warnings,cargo build --locked --release, and the unconfigured binary exits withconfiguration error: ....Release and deploy approved by Michiel in Decision Inbox Q-097.
🤖 Generated with Claude Code