Configuring Curator in scripted deployments

Use the information in this section if you must configure Curator in scripted deployments.

Prerequisites

Cluster logging and Elasticsearch must be installed.
Set cluster logging to the unmanaged state.

Procedure

Use the following snippets to configure Curator in your scripts:

For scripted deployments
1. Create and modify the configuration:
  1. Copy the Curator configuration file and the {product-title} custom configuration file from the Curator configuration map and create separate files for each:
    
    $ oc extract configmap/curator --keys=curator5.yaml,config.yaml --to=/my/config
  2. Edit the /my/config/curator5.yaml and /my/config/config.yaml files.
2. Delete the existing Curator config map and add the edited YAML files to a new Curator config map.
  $ oc delete configmap curator ; sleep 1 $ oc create configmap curator \ --from-file=curator5.yaml=/my/config/curator5.yaml \ --from-file=config.yaml=/my/config/config.yaml \ ; sleep 1
  The next iteration will use this configuration.
If you are using the action file:
1. Create and modify the configuration:
  1. Copy the Curator configuration file and the action file from the Curator configuration map and create separate files for each:
    
    $ oc extract configmap/curator --keys=curator5.yaml,actions.yaml --to=/my/config
  2. Edit the /my/config/curator5.yaml and /my/config/actions.yaml files.
2. Delete the existing Curator config map and add the edited YAML files to a new Curator config map.
  $ oc delete configmap curator ; sleep 1 $ oc create configmap curator \ --from-file=curator5.yaml=/my/config/curator5.yaml \ --from-file=actions.yaml=/my/config/actions.yaml \ ; sleep 1
  The next iteration will use this configuration.