Petals ESB CLI

Add a configuration to select the network interface used by the embedded HTTP server

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major 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
  • Description:
    Hide

    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.

    Show
    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.
  • Environment:
    Linux

Issue Links

Activity

Christophe DENEUX made changes - Tue, 18 Jun 2019 - 15:46:34 +0200
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 ]
Christophe DENEUX made changes - Tue, 25 Oct 2022 - 16:02:46 +0200
Resolution Duplicate [ 3 ]
Status New [ 10000 ] Resolved [ 10004 ]
Fix Version/s 3.2.0 - Petals CLI [ 10914 ]
Christophe DENEUX made changes - Tue, 25 Oct 2022 - 16:03:00 +0200
Link This issue duplicates PETALSESBCLI-87 [ PETALSESBCLI-87 ]
Hide
Christophe DENEUX added a comment - Tue, 25 Oct 2022 - 16:03:55 +0200

'embedded.http.host' was already introduced by PETALSESBCLI-87, but not documented. User documentation is now updated.

Show
Christophe DENEUX added a comment - Tue, 25 Oct 2022 - 16:03:55 +0200 'embedded.http.host' was already introduced by PETALSESBCLI-87, but not documented. User documentation is now updated.
Christophe DENEUX made changes - Tue, 25 Oct 2022 - 16:04:20 +0200
Fix Version/s 3.2.0 - Petals CLI [ 10914 ]
Hide
Christophe DENEUX added a comment - Wed, 26 Oct 2022 - 11:10:07 +0200

This issue is not duplicated. No parameter to select the network interface exists, but a confusion with the parameter of the alias 'embedded.http'.
With PETALSESBCLI-184, 'embedded.http' is no more an alias, so the parameter 'embedded.http.host' was automatically removed. We must reintroduce it to configure the network interface to use to reach the embedded HTTP server from outside.

Show
Christophe DENEUX added a comment - Wed, 26 Oct 2022 - 11:10:07 +0200 This issue is not duplicated. No parameter to select the network interface exists, but a confusion with the parameter of the alias 'embedded.http'. With PETALSESBCLI-184, 'embedded.http' is no more an alias, so the parameter 'embedded.http.host' was automatically removed. We must reintroduce it to configure the network interface to use to reach the embedded HTTP server from outside.
Christophe DENEUX made changes - Wed, 26 Oct 2022 - 11:10:07 +0200
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Duplicate [ 3 ]
Christophe DENEUX made changes - Wed, 26 Oct 2022 - 11:10:10 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Christophe DENEUX added a comment - Wed, 26 Oct 2022 - 15:16:50 +0200

Added in trunk

Show
Christophe DENEUX added a comment - Wed, 26 Oct 2022 - 15:16:50 +0200 Added in trunk
Christophe DENEUX made changes - Wed, 26 Oct 2022 - 15:16:50 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Resolved Resolved
1225d 4h 30m
1
Christophe DENEUX
Tue, 25 Oct 2022 - 16:02:46 +0200
Resolved Resolved Open Open
19h 7m
1
Christophe DENEUX
Wed, 26 Oct 2022 - 11:10:07 +0200
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Wed, 26 Oct 2022 - 11:10:10 +0200
In Progress In Progress Resolved Resolved
4h 6m
1
Christophe DENEUX
Wed, 26 Oct 2022 - 15:16:50 +0200

People

Dates

  • Created:
    Tue, 18 Jun 2019 - 11:32:05 +0200
    Updated:
    Wed, 26 Oct 2022 - 15:16:50 +0200
    Resolved:
    Wed, 26 Oct 2022 - 15:16:50 +0200