Migrate bundles to new application directory structure
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Migrate bundles to new application directory structure
The information in this topic applies to you if you are upgrading to the current version of Splunk from a version of Splunk that is older than 3.3.
Starting with version 3.3, Splunk's custom bundle directory structure and terminology have both changed. The existing directory structure and nomenclature will be supported in 3.3, but a switch to the new structure will be enforced in a future release. For detailed information about the new applications directory structure, refer to the documentation about configuration files.
Splunk provides a script for migrating your existing bundles directories to the new structure. This script is not run automatically, and can be run on a per-bundle/application basis. You must restart Splunk after you run the script, each time you run it.
Things to consider
- You must restart Splunk for changes to take effect.
- Some custom bundles may not work after migration; in particular, bundles that contain conf files or scripts that refer to hard-coded paths might break, since migration moves files around. Consider using relative paths for flexibility.
Run the migration script
To run the script and migrate all your bundles to the new application directory structure, from $SPLUNK_HOME, run:
./splunk migrate bundle [-name value]
To migrate a single bundle to the new structure, add -name [name of the bundle]. For example:
./splunk migrate bundle -name local
./splunk migrate bundle -name code
./splunk migrate bundle
This documentation applies to the following versions of Splunk: 3.3 , 3.3.1 , 3.3.2 , 3.3.3 , 3.3.4 , 3.4 , 3.4.1 , 3.4.2 , 3.4.3 , 3.4.5 , 3.4.6 , 3.4.8 , 3.4.9 , 3.4.10 , 3.4.11 , 3.4.12 , 3.4.13 , 3.4.14 View the Article History for its revisions.