Add cifmw_build_containers_force flag to build tcib containers always in meta content provider

Sometimes we want to build tcib content provider irrespective of gating
repo. In order to do that there is no way to do that.

By adding cifmw_build_containers_force flag allows to build the containers
in meta content provider.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>

Author: raukadah

ci/playbooks/meta_content_provider/meta_content_provider.yml

@@ -47,7 +47,9 @@
     - name: Build openstack services container when gating repo exists
       when:
         - "'os-net-config' not in zuul_change_list"
-        - _gating_repo.stat.exists
+        # Note: cifmw_build_containers_force var is used to run build_containers
+        # role in the meta content provider irrespective of gating repo.
+        - _gating_repo.stat.exists or cifmw_build_containers_force | default('false')
       block:
         # It is needed to install built python-tcib package on the controller
         - name: Populate gating repo in /etc/yum.repos.d

roles/build_containers/README.md

@@ -35,3 +35,7 @@ become - Required to install and execute tcib
 * `cifmw_build_containers_hotfix_tag`: (String) The tag of the container image.
 * `cifmw_build_containers_run_hotfix`: (boolean) conditional variable for executing build_containers.
 * `cifmw_build_containers_install_from_source`: (boolean) Install tcib from RPM.
+
+### Parameters used in meta-content-provider
+
+* `cifmw_build_containers_force`: (Boolean) Force run build_containers role irrespective of gating repo. Default to `false`.