Petals ESB CLI

Port in artifact URL should no be 0 when serving artifacts for deployment

Details

  • Type: Bug Bug
  • 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: Command 'deploy'
  • Security Level: Public
  • Description:
    Hide

    When I deploy a local artifact to a distant Petals container with CLI using 'embedded.http.port' property with value 0, or using the default property value.

    What is does (and should not):

    • it uses the value 0 for the port on the served artifact URL, thus the distant Petals container cannot download the artifact.

    What it should do:

    • it should use the value of the actual serving port of the artifact server.
    Show
    When I deploy a local artifact to a distant Petals container with CLI using 'embedded.http.port' property with value 0, or using the default property value. What is does (and should not):
    • it uses the value 0 for the port on the served artifact URL, thus the distant Petals container cannot download the artifact.
    What it should do:
    • it should use the value of the actual serving port of the artifact server.
  • Environment:
    Linux

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Mon, 24 Oct 2022 - 15:05:12 +0200 - edited

The port value to use to build the URL of the artifact to deploy must be based on ServerConnector.getLocalPort() that returns the port allocated randomly, instead of using directly the value of EmbeddedHttpServerConfig that contains the port value configured.

Show
Christophe DENEUX added a comment - Mon, 24 Oct 2022 - 15:05:12 +0200 - edited The port value to use to build the URL of the artifact to deploy must be based on ServerConnector.getLocalPort() that returns the port allocated randomly, instead of using directly the value of EmbeddedHttpServerConfig that contains the port value configured.
Christophe DENEUX made changes - Mon, 24 Oct 2022 - 15:05:12 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Tue, 25 Oct 2022 - 15:52:36 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Tue, 25 Oct 2022 - 15:53:21 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Tue, 25 Oct 2022 - 15:53:21 +0200 Fixed in trunk
Christophe DENEUX made changes - Tue, 25 Oct 2022 - 15:53:21 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 3.1.2 - Petals CLI [ 10914 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1216d 22h 54m
1
Christophe DENEUX
Mon, 24 Oct 2022 - 15:05:12 +0200
Open Open In Progress In Progress
1d 47m
1
Christophe DENEUX
Tue, 25 Oct 2022 - 15:52:36 +0200
In Progress In Progress Resolved Resolved
45s
1
Christophe DENEUX
Tue, 25 Oct 2022 - 15:53:21 +0200



People

Dates

  • Created:
    Tue, 25 Jun 2019 - 16:10:36 +0200
    Updated:
    Tue, 25 Oct 2022 - 15:53:21 +0200
    Resolved:
    Tue, 25 Oct 2022 - 15:53:21 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.