Conversation
jsanchezIR
approved these changes
Apr 13, 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.
🌐 Add Proxy Support to Deployment Scripts
This PR introduces optional proxy support across the on-prem deployment automation, enabling installations in environments where outbound traffic must go through an HTTP/HTTPS proxy.
✅ What’s Included
The scripts now automatically detect standard proxy environment variables if they are set:
HTTP_PROXY, HTTPS_PROXY, NO_PROXY
Lowercase equivalents (http_proxy, etc.)
Optional: FTP_PROXY, ALL_PROXY
No changes are required for users who do not use a proxy.
Proxy variables are now passed into temporary containers used during:
Podman image customization (build_podman_secret_image)
This ensures package installs and image preparation steps work correctly behind a proxy.
Proxy variables are injected into generated systemd units:
Docker (iriusrisk-docker.service)
Podman (iriusrisk-podman.service)
This ensures all runtime containers inherit proxy configuration automatically.
Added a new “Proxy Configuration (Optional)” section to the README
Includes step-by-step setup instructions and verification guidance
🔁 Backward Compatibility
Fully backward-compatible
If no proxy variables are set, the deployment behaves exactly as before
No breaking changes to existing workflows
🧪 Testing Considerations
Tested scenarios:
✅ No proxy configured (baseline behavior unchanged)
✅ Proxy variables set → successful install and container runtime
✅ Podman image customization behind proxy
✅ Systemd services inherit proxy configuration correctly
📌 Summary
This change makes the deployment scripts compatible with restricted network environments while remaining completely transparent for standard installations.