Deployed 72eecd4 to v2025.2.0 with MkDocs 1.5.3 and mike 2.1.1

Author: Lasyavns

v2025.2.0/authmechanisms/index.html

@@ -2402,7 +2402,7 @@ <h2 id="session-token-based-authentication">Session token-based authentication</
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <ul>
-<li>createTenancyConfig.py script will use the config file located at /cd3user/.oci path. And toolkit supports profile name as DEFAULT only.</li>
+<li>connectCloud.py script will use the config file located at /cd3user/.oci path. And toolkit supports profile name as DEFAULT only.</li>
 <li>Generated session token will have maximum 60 minutes validity. You will have to follow from step 1 if new session token is required after expiry. The User should have administrator access to the tenancy to use complete functionality of the toolkit.</li>
 </ul>
 </div>

v2025.2.0/cd3-jenkins/index.html

@@ -2422,7 +2422,7 @@ <h1 id="set-up-oci-using-automation-toolkit-with-jenkins"><strong>Set Up OCI usi
 <hr />
 <p>Jenkins integration with the toolkit is provided to jump start your journey with CI/CD for IaC in OCI. A beginner level of understanding of Jenkins is required.</p>
 <h2 id="pre-reqs-for-jenkins-configuration"><strong>Pre-reqs for Jenkins Configuration</strong></h2>
-<p>The required configurations for Jenkins setup are done when executing createTenancyConfig.py in <a href="../connect-container-to-oci-tenancy"><u>Connect CD3 Container to OCI Tenancy</u></a>. Here are the validation steps:</p>
+<p>The required configurations for Jenkins setup are done when executing connectCloud.py in <a href="../connect-container-to-oci-tenancy"><u>Connect CD3 Container to OCI Tenancy</u></a>. Here are the validation steps:</p>
 <ul>
 <li>jenkins.properties file is created under <code>/cd3user/tenancies/jenkins_home</code>  as per input parameters in tenancyconfig.  properties<br></li>
 <li>An Object Storage bucket is created in OCI in the specified compartment to manage tfstate remotely. <br></li>
@@ -2437,7 +2437,7 @@ <h2 id="bootstrapping-of-jenkins-in-the-toolkit"><strong>Bootstrapping of Jenkin
 <div class="admonition info">
 <p class="admonition-title">Jenkins configuration for new prefix</p>
 <ul>
-<li>If createTenancyConfig.py has been run again for a new prefix, then first kill the existing jenkins process and start new after that.</li>
+<li>If connectCloud.py has been run again for a new prefix, then first kill the existing jenkins process and start new after that.</li>
 <li>Command to get Jenkins process id -  <code>ps -ef | grep jenkins</code></li>
 <li>Command to kill - <code>kill -9 &lt;process_id&gt;</code></li>
 <li>Start Jenkins using - <code>/usr/share/jenkins/jenkins.sh &amp;</code></li>

v2025.2.0/cd3validator/index.html

@@ -2429,7 +2429,7 @@ <h1 id="cd3-validator-features">CD3 Validator Features</h1>
 <p><I>Compartment Network does not exist in OCI.</I>→ This error means that the component is not found in OCI. So, please make sure to create the Compartment "Network" before validating other tabs.</p>
 </li>
 <li>
-<p><I>Either "Region" ashburn is not subscribed to tenancy or toolkit is not yet configured to be used for this region.</I> → If this is a new region subscribed to the tenancy after toolkit was setup initially then Please re run createTenancyConfig.py with same connectOCI.properties to configure the toolkit with the new region.</p>
+<p><I>Either "Region" ashburn is not subscribed to tenancy or toolkit is not yet configured to be used for this region.</I> → If this is a new region subscribed to the tenancy after toolkit was setup initially then Please re run connectCloud.py with same connectOCI.properties to configure the toolkit with the new region.</p>
 </li>
 <li>
 <p>For policy statements like below:<br>

v2025.2.0/connect-container-to-oci-tenancy/index.html

@@ -2636,7 +2636,7 @@ <h1 id="connect-cd3-container-to-oci-tenancy"><strong>Connect CD3 Container to O
             <td>outdir_structure_file.properties</td>
             <td>/cd3user/tenancies/&lt;prefix&gt;/&lt;prefix&gt;_outdir_structure_file</td>
             <td>Customer Specific properties file for outdir structure.
-            This file will not be generated if 'outdir_structure_file' parameter was set to empty(single outdir)in connectOCI.properties while running createTenancyConfig.py</td>
+            This file will not be generated if 'outdir_structure_file' parameter was set to empty(single outdir)in connectOCI.properties while running connectCloud.py</td>
         </tr>
         <tr>
             <td>Region based directories</td>
@@ -2727,7 +2727,7 @@ <h1 id="connect-cd3-container-to-oci-tenancy"><strong>Connect CD3 Container to O
 <p><br></p>
 <div class="admonition abstract">
 <p class="admonition-title">Subscribing to a new OCI Region?</p>
-<p>When a new region is subscribed to the tenancy, rerun <code>createTenancyConfig.py</code> by using the same <code>connectOCI.properties</code> file that was originally used.<br>
+<p>When a new region is subscribed to the tenancy, rerun <code>connectCloud.py</code> by using the same <code>connectOCI.properties</code> file that was originally used.<br>
 ✅ It will create new directory for the new region under <code>/cd3user/tenancies/&lt;prefix&gt;/terraform_files</code> without modifying the existing ones <br>
 ✅ It will also commit the latest terraform_files folder to OCI DevOps GIT repo.</p>
 </div>

v2025.2.0/delete-prefix/index.html

@@ -2364,10 +2364,10 @@
 <h1 id="delete-prefix-and-its-supporting-resources-in-oci"><strong>Delete prefix and its supporting resources in OCI</strong></h1>
 <hr />
 <p>Users can delete an existing prefix if they are not using it anymore to ensure no prefix-specific residual resources or components remain and also to avoid naming conflicts in future executions.<br>
-🔁  This is also beneficial for users who want to re-run <code>createTenancyConfig.py</code> with the same prefix after an unsuccessful execution.</p>
+🔁  This is also beneficial for users who want to re-run <code>connectCloud.py</code> with the same prefix after an unsuccessful execution.</p>
 <p><br></p>
-<p><span style="color: teal;"><b>Resources created with createTenancyConfig.py execution:</b></span></p>
-<p>When executing createTenancyConfig.py during <a href="../connect-container-to-oci-tenancy"><u>Connect Container to OCI</u></a>, the following components are created:</p>
+<p><span style="color: teal;"><b>Resources created with connectCloud.py execution:</b></span></p>
+<p>When executing connectCloud.py during <a href="../connect-container-to-oci-tenancy"><u>Connect Container to OCI</u></a>, the following components are created:</p>
 <ul>
 <li>Config files under <code>/cd3user/tenancies/&lt;prefix&gt;</code> folder</li>
 </ul>

v2025.2.0/faq/index.html

@@ -2368,7 +2368,7 @@ <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
 <p>Make sure to use a clean outdir without any .tfvars or .tfstate file. Also use a blank CD3 Excel sheet as export process will overwrite the data in the    respective tab.</p>
 <p><strong>3. If I am already using the toolkit and my OCI tenancy has been subscribed to a new region, how do i use the new region with toolkit?</strong>
 <br><br />
-Re-run createTenancyConfig.py with same details in tenancyConfig.properties file. It will keep existing region directories as is and create new directory for newly subscribed region.</p>
+Re-run connectCloud.py with same details in connectOCI.properties file. It will keep existing region directories as is and create new directory for newly subscribed region.</p>
 <p><strong>4. How do I upgrade an existing version of the toolkit to the new one without disrupting my existing tenancy files/directories?</strong>
 <br><br />
  Check out <a href="../upgrade-toolkit"><u>Steps to Upgrade Your Toolkit</u></a></p>

v2025.2.0/group-tf-files/index.html

@@ -2381,15 +2381,15 @@ <h1 id="grouping-set-of-resources-into-a-single-tf-state-file">Grouping set of r
 <ul>
 <li>Do not modify the OCI service Names specified on the left hand side.Modify the directory name specified on Right Hand Side only.</li>
 <li>Directory will be created for that service under &lt;region&gt; directory. Do not provide absolute path.</li>
-<li>To make any changes to the directory structure later, it is necessary to rerun the <code>createTenancyConfig.py</code> script from scratch.</li>
+<li>To make any changes to the directory structure later, it is necessary to rerun the <code>connectCloud.py</code> script from scratch.</li>
 <li>It is mandatory to specify the directory name for each service.</li>
 </ul>
 </div>
 <p><img width="953" alt="image" src="../images/grouptf-2.png"></p>
 <p>Here, the network and nsg directories have been renamed to <strong>demo_network</strong> and <strong>demo_nsg</strong> respectively. The next steps to run the toolkit remain the same as specified in <a href="../greenfield-cli"><u>Greenfield workflow</u></a></p>
 <ol>
 <li>
-<p>Run <code>python createTenancyConfig.py connectOCI.properties</code> from <code>cd3_automation_toolkit</code> folder. This will create prefix folder as <code>/cd3user/tenancies/&lt;prefix&gt;/</code> and configure a seperate directory for each service inside region folder subscribed to the tenancy.</p>
+<p>Run <code>python connectCloud.py oci connectOCI.properties</code> from <code>cd3_automation_toolkit</code> folder. This will create prefix folder as <code>/cd3user/tenancies/&lt;prefix&gt;/</code> and configure a seperate directory for each service inside region folder subscribed to the tenancy.</p>
 </li>
 <li>
 <p>Go to <code>/cd3user/tenancies/&lt;prefix&gt;/&lt;prefix&gt;_setUpOCI.propertiesfile</code> and add the CD3 Excel path. </p>
@@ -2418,7 +2418,7 @@ <h1 id="grouping-set-of-resources-into-a-single-tf-state-file">Grouping set of r
    <img alt="image" src="../images/grouptf-5.png" /></p>
 </li>
 <li>
-<p>Run <code>python createTenancyConfig.py connectOCI.properties</code> from  <code>cd3_automation_toolkit</code> folder. This will create prefix folder as <code>/cd3user/tenancies/&lt;prefix&gt;/</code> and tfvars/state file for each service inside the region folder subscribed for the region.</p>
+<p>Run <code>python connectCloud.py oci connectOCI.properties</code> from  <code>cd3_automation_toolkit</code> folder. This will create prefix folder as <code>/cd3user/tenancies/&lt;prefix&gt;/</code> and tfvars/state file for each service inside the region folder subscribed for the region.</p>
 </li>
 <li>
 <p>Rest of the steps to run the toolkit remain the same.</p>

v2025.2.0/isv_jenkins/index.html

@@ -2522,7 +2522,7 @@ <h2 id="connect-container-to-oci-tenancy">Connect container to OCI Tenancy</h2>
 <ul>
 <li>
 <p>Initialise the environment to use the Automation Toolkit.
-<div class="language-text highlight"><pre><span></span><code><span id="__span-4-1"><a id="__codelineno-4-1" name="__codelineno-4-1" href="#__codelineno-4-1"></a>python createTenancyConfig.py connectOCI.properties
+<div class="language-text highlight"><pre><span></span><code><span id="__span-4-1"><a id="__codelineno-4-1" name="__codelineno-4-1" href="#__codelineno-4-1"></a>python connectCloud.py oci connectOCI.properties
 </span></code></pre></div></p>
 <div class="admonition note">
 <p class="admonition-title">Note</p>

v2025.2.0/multiple-prefixes/index.html

@@ -2367,7 +2367,7 @@ <h1 id="connect-container-to-oci-tenancy-multiple-prefixes"><strong>Connect cont
 <div class="admonition note">
 <p class="admonition-title">Multi-prefix with Jenkins</p>
 <ul>
-<li>With the toolkit release v2024.4.1, the toolkit supports executing createTenancyConfig.py with different values for <strong>prefix</strong> per container when using Jenkins.</li>
+<li>With the toolkit release v2024.4.1, the toolkit supports executing connectCloud.py with different values for <strong>prefix</strong> per container when using Jenkins.</li>
 </ul>
 </div>
 <p><br></p>
@@ -2381,13 +2381,13 @@ <h1 id="connect-container-to-oci-tenancy-multiple-prefixes"><strong>Connect cont
 </ul>
 <div class="admonition tip">
 <p class="admonition-title">Tip</p>
-<p>You can copy connectOCI.properties file as tenancyconfig_&lt;prefix&gt;.properties and edit this file instead of directly editing connectOCI.properties.<br>
-This will help retain the input properties files used for different executions of the createTenancyConfig.py</p>
+<p>You can copy connectOCI.properties file as connectOCI_&lt;prefix&gt;.properties and edit this file instead of directly editing connectOCI.properties.<br>
+This will help retain the input properties files used for different executions of the connectCloud.py</p>
 </div>
 <ul>
 <li>Different values can be specified for other parameters as well. For instance, one prefix can be configured to have <strong>multiple outdir structure</strong> for the generated terraform files, while another prefix can be set with a <strong>single outdir structure</strong>.</li>
-<li>Execute <strong>createTenancyConfig.py</strong> with modified <strong>connectOCI.properties</strong> or <strong>tenancyconfig_&lt;prefix&gt;.properties</strong>.</li>
-<li>After executing <strong>createTenancyConfig.py</strong>, the following screenshots show how the environment specific out directories look like when using the toolkit with CLI and with Jenkins.</li>
+<li>Execute <strong>connectCloud.py</strong> with modified <strong>connectOCI.properties</strong> or <strong>connectOCI_&lt;prefix&gt;.properties</strong>.</li>
+<li>After executing <strong>connectCloud.py</strong>, the following screenshots show how the environment specific out directories look like when using the toolkit with CLI and with Jenkins.</li>
 </ul>
 <p><br></p>
 <p><span style="color: teal; font-weight: bold;"> Multi Prefix with CLI</span></p>

v2025.2.0/remotestate/index.html

@@ -2375,12 +2375,12 @@ <h1 id="store-terraform-state-into-object-storage-bucket">Store Terraform State
 <p><br></p>
 <ul>
 <li>Toolkit provides the option to store terraform state file(tfstate) into Object Storage bucket.</li>
-<li>This can be achieved by setting <code>use_remote_state=yes</code> under Advanced Parameters in <code>connectOCI.properties</code> file while executing <code>createTenancyConfig.py</code>.</li>
+<li>This can be achieved by setting <code>use_remote_state=yes</code> under Advanced Parameters in <code>connectOCI.properties</code> file while executing <code>connectCloud.py</code>.</li>
 <li>
 <p>Upon setting above parameter the script will -</p>
 <ul>
 <li>create a versioning enabled bucket in OCI tenancy in the specified region(if you don't specify anything in <code>remote_state_bucket_name</code> parameter to use an existing bucket)</li>
-<li>create a new customer secret key for the user, and configure it as S3 credentials to access the bucket. Before executing the createTenancyConfig.py script, ensure that the specified user in the DevOps User Details or identified by the user OCID does not already have the maximum limit of two customer secret keys assigned. </li>
+<li>create a new customer secret key for the user, and configure it as S3 credentials to access the bucket. Before executing the connectCloud.py script, ensure that the specified user in the DevOps User Details or identified by the user OCID does not already have the maximum limit of two customer secret keys assigned. </li>
 </ul>
 </li>
 <li>