Defect #2592
closedCzechIdM container with 10.6.3 cannot rebuild application with idm-tool
0%
Description
CzechIdM 10.4.0 was released with upgraded libraries: node, npm, npx. Currently idm-tool can bootstrap node and npm, but cannot bootstrap npx (limitation of used maven plugin).
The unattended build inside container now fails with
11-27 11:20:00.764 INFO --- [ main] e.b.idm.tool.service.impl.MavenManager : [INFO] sh: npx: command not found
IdM in container cannot rebuild itself, therefore it cannot integrate user-supplied modules. Only plain product can be deployed using the standard container.
This can be (hardly) worked-around by supplying whole WAR to the image build process and make
docker build ...
produce complete image including all customizations.Blocker for releasing updated IdM image.
I discussed this with Radek: From IdM standpoint, the npx binary is a build workaround which we need only until we migrate to gulp 4 (in a few months).
Probably the best way is to implement npx install inside the container. We could also just "know issue" this but I am not really sure if it is viable.
Bussiness feedback needed.
Updated by Petr Fišer about 4 years ago
Fixed frontend build in git.aaf09a2 . The backend build fails too - it cannot find repositories on nexus.bcvsolutions.eu.
I consulted this with Radek and this comes with idm-tool pulling dependencies dynamically.
So we need to add repositories into maven configuration, and also a login/pass to access our Nexus.
This is probably not a problem per se, because only paying customers can access full IdM releases... so some Nexus account is probably ok.
But we will need to add support for this into the czechidm-docker image.
I will consult this with Zdenda, just to be sure.
Updated by Petr Fišer about 4 years ago
After today's telco: Radek will adjust idm-tool so it does not need access to nexus.
This ticket will "wait" until then.
Updated by Petr Fišer about 4 years ago
- Status changed from In Progress to Closed
We skipped container for the 10.6.3 version.
Issue reported in this ticket was resolved in CzechIdM product 10.7.0.