Splunk® DB Connect

Deploy and Use Splunk DB Connect

dbx-migration.conf.spec


[encryption]

upgrade = [NONE|PENDING|DONE]
# Defines the migration action (upgrading) for encryption algorithms
# PENDING: migration will take place after the server starts
# NONE: migration is not needed
# DONE: migration was done previously, it is skipped

downgrade = [NONE|PENDING|DONE]
# Defines the migration action (downgrading) for encryption algorithms
# PENDING: migration will take place after the server starts
# NONE: migration is not needed
# DONE: migration was done previously, it is skipped

onError = [FAIL_FAST|FAIL_SAFE]
# Defines how it behaves in case of failures during the migration
# FAIL_FAST: if there is a failure, the migration is stopped and the changes are rolled back
# FAIL_SAFE: if there is a failure, the migration continues and the changes remain
Last modified on 20 July, 2023
Configuration file reference   db_connection_types.conf.spec

This documentation applies to the following versions of Splunk® DB Connect: 3.14.0, 3.14.1, 3.15.0, 3.16.0, 3.17.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters