Page 1 of 1

[SOLVED] Distinguishing between client and server machines.

Published: January 13, 2025 - 2:26 PM
by Etamin
Hello TranquilIT,

We manage client workstations and servers in our WAPT system, all pointing to the same package repository.
We (CISO...) would like the servers to prevent the automatic deployment of certain packages when we update an application in the WAPT console (browsers, etc.).
Is it possible to differentiate between these servers?
I considered disabling WaptExit on these machines, but that seemed drastic and would impact all packages.
Alternatively, we could duplicate the packages, one for the client and one for each server, which would complicate management.
If you have a better solution, please let me know.

Thank you in advance!

Re: Distinction between client machines and servers.

Published: January 13, 2025 - 5:03 PM
by dcardon
Hello Etamin,

you can assign the PROD_SERVER maturity level to the servers. This way, the servers will no longer accept packages with the default PROD maturity level.

When you want to push an update to the servers, you assign them the PROD_SERVER maturity level. The problem is that a package can currently only have one maturity level. Therefore, the packages to be deployed on the servers will need to be duplicated compared to the workstation packages, which will have the PROD maturity level.

Regards,

Denis

Re: Distinction between client machines and servers.

Published: January 13, 2025 - 5:26 PM
by dcardon
Hello again Etamin,

after discussing with Simon, here's an option to avoid duplicating packages:
* Servers have the maturity level PROD,PROD_SERVER
* Client workstations have the maturity level PROD,PROD_CLIENT
* Packages for servers only have the maturity level PROD_SERVER
* Packages for workstations only have the maturity level PROD_CLIENT
* Packages for both have the maturity level PROD only.

Best regards,

Denis

Re: Distinction between client machines and servers.

Published: January 16, 2025 - 08:55
by Clafon
I'm taking the liberty of using this thread; the solution might also interest us. So, how do we create custom maturity levels? For the moment, I only see the pre-programmed ones (PROD, PREPORD, DEV)

Re: Distinction between client machines and servers.

Published: January 16, 2025 - 09:37
by sfonteneau
Hello,

the graphical interface offers a list of PROD, PREPROD, and DEV, but you can type whatever you want using the keyboard.

Similarly, in the dynamic package configuration interface, you can write the maturity list like this:

PROD,TOTO,TATA

Re: Distinction between client machines and servers.

Published: January 16, 2025 - 09:38
by Clafon
Awesome, thanks!