From 5dbaef03b3c064bace1d13358b41b2d9ae817e5b Mon Sep 17 00:00:00 2001 From: Abraham Chavez Date: Thu, 29 Feb 2024 10:39:29 -0800 Subject: [PATCH] fixup! Parameterize reindex job in GitLab with catalog to reindex (#5336) --- OPERATOR.rst | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/OPERATOR.rst b/OPERATOR.rst index 93219b0dfd..8e23eadcaa 100644 --- a/OPERATOR.rst +++ b/OPERATOR.rst @@ -252,14 +252,17 @@ Reindexing a specific catalog in GitLab ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From the GitLab console, select the reindex job for the pipeline that needs -reindexing of any targeted catalog/s. From there, you should see an option for -defining key, value pair of variables. These are to be used as an environement -variables in this run to enforce any last minute configuration changes. - -Set ``Key=azul_current_catalog`` and Value to the desired catalog/s to be -index, for example, if we want to only index ``dcp3``, then set ``Value=dcp3``. -Once you've confirm this is the desired configuration, start the reindex by -clicking on ``Run job``. +reindexing of a targeted catalog. From there, you should see an option for +defining a key, value pair of variables. These are to be used as an +environement variable in this run, to enforce any last minute configuration +changes. + +Set ``Key`` to ``azul_current_catalog``, and ``Value`` to the desired catalog to be +indexed, for example, ``dcp3``. Once you've confirm this is the desired +configuration, start the reindex by clicking on ``Run job``. + +Repeat these steps to index any additional catalogs. + Updating the AMI for GitLab instances ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^