For API user who wants to connect to/interact w/ Humio, there needs to be an API token set up. And according to the Humio docs, this can be retrieved from Humio UI.
Our scenario is to automate the Humio deploy (for demo purpose), and setup the consumer (as the API user) w/ specified Humio API endpoint and API token, so that all can be done in automation scripts from end to end.
Humio service URL: The fully qualified Humio query API URL for the Humio instance, for example: http:///api/v1/repositories//query
API token: The connection token for the Humio instance.
If the API token can only be retrieved by UI, hence not able to automate, then we will have to split the whole automation process into two phases:
1) Automate Humio deploy;
2) Tell user where to get the API token from UI and fill into a configuration file, then kick off the remaining automation process.
For API user who wants to connect to/interact w/ Humio, there needs to be an API token set up. And according to the Humio docs, this can be retrieved from Humio UI.
Our scenario is to automate the Humio deploy (for demo purpose), and setup the consumer (as the API user) w/ specified Humio API endpoint and API token, so that all can be done in automation scripts from end to end.
If the API token can only be retrieved by UI, hence not able to automate, then we will have to split the whole automation process into two phases: 1) Automate Humio deploy; 2) Tell user where to get the API token from UI and fill into a configuration file, then kick off the remaining automation process.
Any suggestion?