Checking the webservice with curl

One of the cool things of using open protocols and interfaces is that you are not limited to use special tooling and can resort to tools you are familiar with. No need to use some unknown programming language or to throw huge amounts of money at some company to get access to the data in your system. This post will explain how you can access the API of your opsi server with curl.

Read more…

Exit-Codes for opsi-admin

Since opsi-utils 4.0.6.3 opsi-admin will fail with appropriate exit codes when used non-interactive to make writing scripts and reacting to failure easier.

The old behaviour was that every call in non-interactive mode - usually by supplying -d - returned an exit-code of 0. This made it very hard to check if something went wrong during such a call.

The new opsi-admin will return an appropriate exit-code when things fail:

  • Exit code 1 will be returned whenever the call itself is problematic - unknown method or wrong/missing parameters.
  • Exit code 2 will be returned when the call to the API was correct but the executed method did return an error.

If you rely on the old behaviour where everything returned exit code 0 you now need to supply --exit-zero to your call of opsi-admin.

Hello World

For many Hello World is the first thing they type when trying a new system.

Having a blog centered around opsi for sure is something new. Therefore this is our hello world!

Opsi - as most of you probably know - is a reliable and flexible open source client management tool. We, the opsi developers, want to use this blog as a platform to allow for a look into the development, for sharing tips and insights into the various facets we experience every day.