Skip to content

Include the MKP build number in the Client Script and server script #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
swampdogmash opened this issue Nov 14, 2024 · 3 comments
Open

Comments

@swampdogmash
Copy link
Contributor

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

@HenriWahl
Copy link
Owner

@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.

@swampdogmash
Copy link
Contributor Author

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.

Image

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.

@HenriWahl
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants