You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to include the MKP build number (version - for example 2.5.2 was last build as of 2024-11-14) into the client script and server script at build time when you generate the MKP so that it is more obvious if things have updated correctly or not?
Andy
The text was updated successfully, but these errors were encountered:
@swampdogmash the build magic happens in the supplied Docker image made of the Dockerfile. The build-entrypoint.sh uses the build-modify-extension.py to modify the package info. If you want to add more build information this would be the starting point.
Fingers crossed this should be now included in #91
This is how it looks when you have a 2.3.0p12 agent on a host that has the yum plugin with the new CMK_VERSION="x.x.x" included in the top of the script.
This should make it easier for anyone deploying the script manually to know which version it is, and for those who use the bakery, you can at least audit what version of the plugin you have.
Henri
Is there a way to include the MKP build number (version - for example 2.5.2 was last build as of 2024-11-14) into the client script and server script at build time when you generate the MKP so that it is more obvious if things have updated correctly or not?
Andy
The text was updated successfully, but these errors were encountered: