feat(console): NGINX connection fields in ⚙ Setup - #58
Merged
Conversation
The ④ Mitigate "Apply on your own NGINX" panel + its help told the operator to set NGINX_SSH_* "in ⚙ Setup", but Setup had no NGINX fields — the only way to point it at the box was hand-editing .env. Added the NGINX_SSH_* keys to MANAGED_KEYS (so the generic Setup config editor renders them as fields) with NGINX_SSH_PASSWORD in SECRET_KEYS (the key PATH is not secret), plus a NGINX + App Protect card in Setup's Advanced integrations with a live status readout (loadNginx → /api/nginx-lab), mirroring the BIG-IP card. +2 tests. Co-Authored-By: Claude Opus 4.8 <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.
Follow-up to #57 (merged). The ④ Mitigate "Apply on your own NGINX" panel and its help text tell the operator to set
NGINX_SSH_*"in ⚙ Setup" — but Setup had no NGINX fields, so the only way to point the copilot at the box was hand-editing.env. (The BIG-IP has its Setup fields; NGINX was missed when the panel was added.)NGINX_SSH_*keys toMANAGED_KEYSso the generic Setup config editor renders them as editable fields;NGINX_SSH_PASSWORDis inSECRET_KEYS(redacted), the key path is not secret (echoed so the page shows what's set).loadNginx→/api/nginx-lab), mirroring the BIG-IP card.+2 tests (config exposes the keys / password redacted; the Setup card + loader are wired). Verified live: Setup manages all 9 NGINX fields and the card reads "nginx-plus-r37.0.4 · App Protect: loaded".
🤖 Generated with Claude Code