In this article, will explore a method for deploying the SHCluster bundle through the REST API by using a curl command. The investigation section offers further insights into the flags related to lookups and default applications.
Let us delve deeper into the flags associated with lookups and default applications.
It is important to understand that the parameters "-preserve-lookups true" and "-push-default-apps true" do not apply in the context of the REST API call.
Should there be a requirement to use these parameters, ensure they are configured in the configuration file and reference the appropriate configuration files for the specified parameters.
Configuration relevant to preserve lookup:
[shclustering]
deployer_lookups_push_mode = preserve_lookups | always_preserve | always_overwrite | overwrite_on_change
Refer to: preserve-lookups-true
If you are using the preserve_lookups mode to push the bundle to the search head cluster, set the -preserve-lookups flag to true to preserve the populated lookup tables for your apps:
splunk apply shcluster-bundle -target <URI>:<management_port> -preserve-lookups true -auth <username>:<password>
For more information refer to: preserve_lookups
To deploy the SHCluster bundle using the REST API, one can execute this curl command:
curl -ku admin https://<deployer_host>:8089/services/apps/deploy -d 'target=https://<shcluster_captain_host>:8089&action=all&advertising=true' -X POST
Where:
a. Deployer Host: Substitute <deployer_host> with the actual hostname or IP address of the deployer (for example, deployer.example.com).
b. SHCluster Captain: Make sure to replace <shcluster_captain_host> with the correct address of the SHCluster captain (like shc-captain.example.com).
c. Port 8089: Verify that port 8089 is open and accessible between the deployer and the SHCluster captain. Check for any network connectivity issues that might hinder access.
d. Remote Execution:When executing this command from a terminal on a different machine (not the deployer), make sure that the deployer host can be accessed from the current terminal.The deployer must be accessible via its hostname or IP address.
PropagateSHCconfigurationchanges
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |