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!
[SOLVED] Distinguishing between client and server machines.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
