Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.1.1 - Petals CLI
-
Fix Version/s: 3.2.0 - Petals CLI
-
Component/s: Configuration
-
Security Level: Public
-
- Environment:
- Linux
Issue Links
| Duplicate | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Add embedded.http.host for Petals CLI | Add a configuration to select the network interface used by the embedded HTTP server |
| Fix Version/s | 3.1.2 - Petals CLI [ 10914 ] | |
| Affects Version/s | 3.1.1 - Petals CLI [ 10905 ] | |
| Affects Version/s | 3.1.2 - Petals CLI [ 10914 ] | |
| Priority | Major [ 3 ] | |
| Description |
When deploying local artifacts (on CLI's machine), I could use the embedded.http.host property on a custom config file to specify the ip or hostname of the HTTP server (of CLI's machine) on which the files would be served.
It would be useful if the IP of CLI's machine is not correctly detected, or if multiple IPs are detected and only one should be used. |
When deploying local artifacts (on Petals CLI's machine), the embedded HTTP server is used to serve the artifact files to the Petals container.
If several network interfaces are available on Petals CLI's machine, we could select which one to use. If the IP of Petals CLI's machine is not correctly detected, we could want to force it. This can be done through a new optional configuration parameter: {{embedded.http.host}}. |
| Component/s | Configuration [ 10470 ] | |
| Component/s | Command 'deploy' [ 10220 ] |
| Resolution | Duplicate [ 3 ] | |
| Status | New [ 10000 ] | Resolved [ 10004 ] |
| Fix Version/s | 3.2.0 - Petals CLI [ 10914 ] |
| Link |
This issue duplicates |
| Fix Version/s | 3.2.0 - Petals CLI [ 10914 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Duplicate [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |