Based on the next discussion.
When i was digging to create custom commands for my users, i realized that you can give description to command Arguments, but not to Macros.
For Macros you either need to be very descriptive in your naming, provide example in the proper field, or provide external documentation about the usage.
I would like to be able to provide description to macros, either on the CMD, STPL or HTPL level, as you can define new macros at each of those steps. Within this evolution, would love to be able to export all this new data within the AWIE module (import/export) so it can be integrated in multiple instances if needed.
On the Command level, we already have fields stored when edited on the web interface but not on the CLAPI as per the next page.
On the Host and Service template level, i belive that this small button has the same purpose, but the same way when exported the description is not exported (and we can’t set it through CLAPI)
The objective would be to clarify the usage of each macro, their exceptions, etc. It can even (why not) contain a link to an external description if needed. The point is to reduce the amount of interaction required for the user to do to understand what information to place on the field when using Centreon.
I would love your feedback on that idea.
Thank you.