Issue: Replace SSH-based port mapping retrieval with a dedicated Port Map API
Description:
The current implementation fetches port mapping data via remote shell commands:
const command = "ssh root@10.15.20.69 'cat /etc/nginx/port_map.json'";
This approach couples application logic to SSH access and CLI tools, increasing latency and security risk.
Recommendation:
Implement a Port Map API exposed by the load balancer or management service to provide and update port mapping data over HTTP(S).
Benefits:
- Removes dependency on SSH and system commands
- Improves performance, reliability, and security
- Enables fine-grained access control and audit logging
- Simplifies integration with front-end or orchestration tools
Issue: Replace SSH-based port mapping retrieval with a dedicated Port Map API
Description:
The current implementation fetches port mapping data via remote shell commands:
This approach couples application logic to SSH access and CLI tools, increasing latency and security risk.
Recommendation:
Implement a Port Map API exposed by the load balancer or management service to provide and update port mapping data over HTTP(S).
Benefits: