Fix Gateway ports syntax for compose

[swarajsaaj]

Fix port string generation in docker-compose.yml file, supporting
app.yml that may contain hostname as well in port-mapping

Fix #14910

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[mraible]

Thanks for your contribution, @swarajsaaj! I believe the version number needs to be removed too. That's what @ndeloof did when he fixed my project in oktadev/java-microservices-examples#23.

If you want to really test things, we should change all instances of docker-compose to docker compose in test-integration/scripts.

[swarajsaaj]

Thanks for your contribution, @swarajsaaj! I believe the version number needs to be removed too. That's what @ndeloof did when he fixed my project in oktadev/java-microservices-examples#23.

If you want to really test things, we should change all instances of docker-compose to docker compose in test-integration/scripts.

Thanks @mraible ,

1. Though the version number is optional now, but we can remove it to be more compliant to latest spec.
2. Yes, it would be great to really test this using integration tests. Made changes in 1460d74

[swarajsaaj]

The pipelines are failing on adding "docker compose" command in test-integration/scripts. The command seems working fine on my machine. Is it possible the new "Compose CLI" support is not installed on azure devops instance?

Update: Added a new step in azure pipeline to install 'compose-cli' and its successful now

[ndeloof]

Compose CLI is indeed a separate component, that is still beta and won't be installed by default.
Probably simpler to use the classic docker-compose until new compose is distributed within the docker CLI system packages

[swarajsaaj]

Yes @ndeloof , its still in "Tech Preview" and the pipelines worked only after adding a step to install the component first.
@mraible Shall we defer it from our test scripts and add it later once this feature is stable (and bundled by default) ?

[mraible]

@swarajsaaj Probably. I was motivated to add support for it since docker-compose tells you to try it.

[swarajsaaj]

@mraible Okay then let's keep the stable 'docker-compose' support for now, and migrate tests to new command once it is stable 😄 (BTW the tests showed that docker compose too is compatible with generated compose files now).
Reverted test command change in f6c9238

[swarajsaaj]

Bounty claimed at https://opencollective.com/generator-jhipster/expenses/40709

[pascalgrimaud]

@swarajsaaj : approved