LOG-1153: Adding logic to perform rollover and delete for json write indices

[ewolinetz]

Description

In anticipation for the ability to store json in Elasticsearch, we need to be able to rollover and delete any json specific write alias based on the policy for either app, infra, or audit (json indices/aliases will follow the pattern <app|infra|audit>-<json-schema-name>-<write|xxxxxx>)

Also cleaned up output of the delete and rollover scripts for ease of use:

========================
Index management delete process starting for infra-json

deleting indices: infra-json-000055
Done!
========================
Index management delete process starting for infra

deleting indices: infra-000074
Done!
========================
Index management rollover process starting for infra-json

Current write index for infra-json-write: infra-json-000057
Checking results from _rollover call
Next write index for infra-json-write: infra-json-000057
Checking if infra-json-000057 exists
Checking if infra-json-000057 is the write index for infra-json-write
Done!
========================
Index management rollover process starting for infra

Current write index for infra-write: infra-000076
Checking results from _rollover call
Next write index for infra-write: infra-000076
Checking if infra-000076 exists
Checking if infra-000076 is the write index for infra-write
Done!

========================
Index management delete process starting for infra-json

No indices to delete
========================
Index management delete process starting for infra

No indices to delete
========================
Index management rollover process starting for infra-json

Current write index for infra-json-write: infra-json-000037
Checking results from _rollover call
Next write index for infra-json-write: infra-json-000037
Checking if infra-json-000037 exists
Checking if infra-json-000037 is the write index for infra-json-write
Done!
========================
Index management rollover process starting for infra

Current write index for infra-write: infra-000056
Checking results from _rollover call
Next write index for infra-write: infra-000056
Checking if infra-000056 exists
Checking if infra-000056 is the write index for infra-write
Done!

/cc @blockloop @periklis

Links

• JIRA: https://issues.redhat.com/browse/LOG-1153

[blockloop]

I think you can eliminate a lot of the copy/pasta if you create a curl function
that calls the ES service with curl with all of the standard flags like this:

function httpES() {
	url="${1}"
	shift
	curl -s "$ES_SERVICE/${1}" \
	    --cacert /etc/indexmanagement/keys/admin-ca \
	    --connect-timeout "${CONNECT_TIMEOUT}" \
	    -H"Authorization: Bearer $(cat /var/run/secrets/kubernetes.io/serviceaccount/token)" \
	    -HContent-Type:application/json \
	    --retry 5 \
	    --retry-delay 5 "$@"
}

function delete() {
	httpES /my/url/here --extra-curl-flag=asdf --another-curl-flag=1234
}

[ewolinetz]

/retest

[blockloop]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: blockloop, ewolinetz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ewolinetz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment