Petals ESB CLI

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

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: 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

People

Assignee:

Christophe DENEUX

Reporter:

Alexandre LAGANE
Watchers:

0

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