davidhou17 · davidhou17 · Sep 14, 2022 · Sep 16, 2022 · Sep 20, 2022 · Sep 21, 2022
diff --git a/.github/prompts/eol-branch.prompt.md b/.github/prompts/eol-branch.prompt.md
@@ -0,0 +1,54 @@
+<!-- Download and configure Github CLI before running -->
+
+You are an agent that will help sunset a version of our docs. The user will provide the version number (e.g. v1.20). Complete the following tasks:
+
+1. Open the `snooty.toml` file and make the following changes:
+
+- Add `eol = true` to line 3.
+- Add the following code where other banners are located in the file. Don't forget the closing quotations.
+
+```
+[[banners]]
+ targets = ["*"]
+ variant = "info"
+ value = """\
+     This version of the documentation is archived and no longer supported. View the `current documentation <https://www.mongodb.com/docs/atlas/cli/current/>`__ to learn how to `upgrade your version of the Atlas CLI <https://www.mongodb.com/docs/atlas/cli/current/install-atlas-cli/>`__.\
+     """
+```
+
+2. Create a new file named `NoindexEntireSource.sh` that contains the following code:
+
+```
+#!/bin/sh
+while getopts p: flag
+do
+    case "${flag}" in
+        p) project=${OPTARG};;
+    esac
+done
+echo "Adding noindex to all files in $project..."
+# Use find to recursively search for .txt files in the source directory and noindex them
+find ~/"$project"/source -type f -name "*.txt" | while read -r file; do
+    sed -i '' "1s%^%.. meta::\n   :robots: noindex, nosnippet \n\n%" "$file"
+done
+```
+
+3. Run the following command in the terminal: `sh <path-to-bash-script>/NoindexEntireSource.sh -p docs-atlas-cli`, replacing `<path-to-bash-script>` with the path to `NoindexEntireSource.sh`.
+
+For example: `sh ~/Projects/NoindexEntireSource.sh -p Projects/docs-atlas-cli`
+
+This script should add the following code to the top of every file in the repo:
+
+```
+.. meta::
+   :robots: noindex, nosnippet 
+```
+
+4. Then, create a PR with these changes by performing the following actions:
+
+- Run `git status`
+- Run `git add -- ':!submodules/mongodb-atlas-cli'`. This is to add all files to the commit except for the submodules files.
+- Generate a short PR description like "Sunset v1.20" and run `gcmsg "<PR description>"` in the terminal.
+- Generate a descriptive PR title like "Sunset Atlas CLI v1.20" and Run `gh pr create --title "(<current-branch>): <title>"`. Replace the placeholders with appropriate values.
+
+The user will finalize the PR via the terminal prompts.
diff --git a/.github/pull-request-template.md b/.github/pull-request-template.md
@@ -0,0 +1,19 @@
+<!-- Add a description of your PR here (optional) -->
+
+- [DOCSP-number](https://jira.mongodb.org/browse/)
+- [STAGING](paste the link to staging here)
+
+- [LATEST BUILD LOG](paste the build here)
+
+### Self-Review Checklist
+
+- [ ] Check that the submodule pulled in the right changes (if applicable).
+- [ ] [Define](https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions) taxonomy [values](https://wiki.corp.mongodb.com/display/DE/Docs+Taxonomy) at top of page.
+- [ ] Add genre facets (tutorial or reference), as in this [example PR](https://github.com/10gen/cloud-docs/pull/5042).
+- [ ] Add programmingLanguage (if necessary).
+- [ ] Add meta keywords (if necessary).
+- [ ] Resolve any new warnings or errors in the build.
+- [ ] Proofread for spelling and grammatical errors.
+- [ ] Check staging for rendering issues.
+- [ ] Confirm links are working.
+
diff --git a/.gitignore b/.gitignore
@@ -1,3 +1,4 @@
 .DS_Store
 .vscode/settings.json
-settings.json
+settings.json
+NoindexEntireSource.sh
diff --git a/.gitmodules b/.gitmodules
@@ -1,3 +0,0 @@
-[submodule "submodules/mongodb-atlas-cli"]
-	path = submodules/mongodb-atlas-cli
-	url = https://github.com/mongodb/mongodb-atlas-cli.git

diff --git a/.vscode/settings.json b/.vscode/settings.json
diff --git a/build.sh b/build.sh
@@ -0,0 +1,7 @@
+# ensures that we always use the latest version of the script
+if [ -f build-site.sh ]; then
+  rm build-site.sh
+fi 
+
+curl https://raw.githubusercontent.com/mongodb/docs-worker-pool/netlify-poc/scripts/build-site.sh -o build-site.sh 
+sh build-site.sh
diff --git a/config/redirects b/config/redirects
@@ -1,4 +1,20 @@
 define: base https://www.mongodb.com/docs/atlas/cli
-define: versions v1.0 master
-
+define: versions v1.0 v1.1 v1.2 v1.3 v1.4 v1.5 v1.6 v1.7 v1.8 v1.9 v1.10 v1.11 v1.12 v1.13 v1.14 v1.15 v1.16 v1.17 v1.18 v1.19 v1.20 v1.21 v1.22 v1.23 master
+symlink: upcoming -> master
+symlink: v1.24 -> master
+symlink: stable -> v1.23
+
 raw: docs/atlas/cli/ -> ${base}/stable/
+raw: docs/atlas/cli/stable/cluster-config-file -> ${base}/stable/reference/json/cluster-config-file
+
+# DOCSP-28477 -- I looked in the docs content source and was unable to find where these malformed links were. so adding redirects to prevent future 404s
+
+raw: docs/atlas/cli/stablecommand/atlas-config-describe/ -> ${base}/stable/command/atlas-config-describe/
+raw: docs/atlas/cli/stablecommand/atlas-liveMigrations-create/ -> ${base}/stable/command/atlas-liveMigrations-create/
+raw: docs/atlas/cli/stablecommand/atlas-liveMigrations-link-create/ -> ${base}/stable/command/atlas-liveMigrations-link-create/
+raw: docs/atlas/cli/stablecommand/atlas-liveMigrations-validation-create/ -> ${base}/stable/command/atlas-liveMigrations-validation-create/
+raw: docs/atlas/cli/stablecommand/atlas-privateEndpoints-onlineArchive-aws-describe/ -> ${base}/stable/command/atlas-privateEndpoints-onlineArchive-aws-describe/
+
+# Atlas CLI Version 1.6 and later
+
+[v1.6-*]: docs/atlas/cli/${version}/cluster-config-file -> ${base}/${version}/reference/json/cluster-config-file
diff --git a/netlify.toml b/netlify.toml
@@ -0,0 +1,6 @@
+[[integrations]]
+name = "snooty-cache-plugin"
+
+[build]
+publish = "snooty/public"
+command = ". ./build.sh"
diff --git a/snooty.toml b/snooty.toml
@@ -1,5 +1,6 @@
 name = "atlas-cli"
-title = "Atlas Command Line Interface"
+title = "Atlas CLI"
+eol = true
 
 intersphinx = [ "https://www.mongodb.com/docs/ops-manager/current/objects.inv",            
                 "https://www.mongodb.com/docs/manual/objects.inv",
@@ -10,22 +11,29 @@ intersphinx = [ "https://www.mongodb.com/docs/ops-manager/current/objects.inv",
 toc_landing_pages = [
   "/atlas-cli-changelog",
   "/atlas-cli-env-variables",
+  "/atlas-cli-automate",
   "/atlas-cli-profiles",
   "/atlas-cli-quickstart",
   "/atlas-cli-tutorials",
+  "/atlas-cli-local-cloud",
   "/command/atlas",
   "/compatibility",
   "/connect-atlas-cli",
   "/install-atlas-cli",
   "/migrate-to-atlas-cli",
+  "/reference/json",
   "/telemetry"
   ]
 
 [constants]
 aagent = "Automation Agent"
+adf = "Atlas Data Federation"
 atlas-cli = "Atlas CLI"
 atlas-cli-full = "MongoDB Atlas CLI"
-atlas-cli-version = "1.1.7"
+atlas-cli-version = "1.23.0"
+ak8so = "Atlas Kubernetes Operator"
+atlas-sp = "Atlas Stream Processing"
+avs = "Atlas Vector Search"
 cloudgov = ":atlas:`MongoDB Atlas for Government </government>`"
 cloudgov-short = "AtlasGov"
 cluster = "cluster"
@@ -39,12 +47,16 @@ data-lake-store = "data store"
 database-deployment = "database deployment"
 database-deployments = "database deployments"
 default-profile = ":ref:`default profile <mcli-profiles>`"
+df = "Data Federation"
+FDI = "Federated Database Instance"
+fdi = "federated database instance"
 mcli = "MongoDB CLI"
 mcli-long = "MongoDB Command Line Interface (``mongocli``)"
 mcli-version = "1.23.1"
 mdbagent = "MongoDB Agent"
-mdbVersion = "6.0"
+mdbVersion = "7.0"
 mongosh = ":binary:`~bin.mongosh`"
+oidc = ":abbr:`OIDC (OpenID Connect)`"
 
 [substitutions]
 a-application = "an Ops Manager Application"
@@ -106,17 +118,24 @@ utc = ":abbr:`UTC (Coordinated Universal Time)`"
 vpc = ":abbr:`VPC (Virtual Private Cloud)`"
 
 [[banners]]
-targets = ["command/atlas-dataLakes*.txt"]
+targets = ["command/atlas-dataLakePipelines*.txt"]
+variant = "warning"
+value = """\
+    **Data Lake is deprecated.** \
+    As of September 2024, Data Lake is deprecated and will reach end-of-life. It will be removed on September 30, 2025. If you use Data Lake, you should migrate to alternative solutions before the service is removed. To learn more, see :adl:`Migration Guide </data-lake-deprecation/>`\
+    """
+
+[[banners]]
+targets = ["*"]
 variant = "info"
 value = """\
-    ``atlas dataLakes`` commands control the functionality previously \ 
-    named Data Lake, which is now called \
-    `Data Federation <https://www.mongodb.com/docs/atlas/data-federation/>`__ \
-    in the Atlas UI. The ``atlas dataLakes`` commands will \ 
-    continue to work for Data Federation without interruption. \ 
-    MongoDB's new \ 
-    `Data Lake <https://www.mongodb.com/docs/datalake/>`__ \ 
-    functionality doesn't include CLI commands. When we introduce a \ 
-    new set of CLI commands for our new Data Lake functionality, we \
-    will reach out to you to prevent any interruption of service.\
+    This version of the documentation is archived and no longer supported. View the `current documentation <https://www.mongodb.com/docs/atlas/cli/current/>`__ to learn how to `upgrade your version of the Atlas CLI <https://www.mongodb.com/docs/atlas/cli/current/install-atlas-cli/>`__.\
     """
+
+[[banners]]
+targets = ["command/atlas-deployments*.txt"]
+variant = "warning"
+value = """\
+    **Public Preview.** \
+    The ``atlas deployments`` command and subsequent related commands are available as a Public Preview. The feature and corresponding documentation may change at any time in the Public Preview stage. To ask questions and provide feedback, see the `Atlas CLI Local Development Community Forum <https://www.mongodb.com/community/forums/tag/local-dev-atlas-cli>`__.\
+    """
diff --git a/source/atlas-cli-automate.txt b/source/atlas-cli-automate.txt
@@ -0,0 +1,114 @@
+.. meta::
+   :robots: noindex, nosnippet 
+
+.. _atlas-cli-automate:
+
+=========================================
+Automate Processes with the {+atlas-cli+}
+=========================================
+
+.. default-domain:: mongodb
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
+To automate a process with the {+atlas-cli+} in a script, use
+the following resources and best practices as guidance.  
+
+To learn how to connect to the {+atlas-cli+} programmatically, see
+the :guilabel:`Programmatic User` tabs on :ref:`connect-atlas-cli`.
+
+Resources for Automation with the {+atlas-cli+}
+-----------------------------------------------
+
+.. list-table:: 
+   :header-rows: 1
+   :widths: 40 60
+
+   * - Resource
+     - Objective
+
+   * - :ref:`atlas-cli-env-vars`
+     - Set environment variables that you can define once and use
+       across all of your scripts.
+
+   * - :ref:`go-template-output`
+     - Use Go templates or |json| paths to customize the output from
+       the {+atlas-cli+}. You can include the anticipated custom output in your scripts.
+
+Best Practices for Automation with the {+atlas-cli+}
+----------------------------------------------------
+
+Follow these best practices when you automate processes with the
+{+atlas-cli+}:
+
+Use |service| Private Keys 
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you create a script to automate processes, we recommend that you
+use |service| :ref:`private keys <atlas-admin-api-access>` to access
+|service|. {+atlas-cli+} login sessions last for twelve hours,
+after which you must login again to access |service|. Use |service|
+:ref:`private keys <atlas-admin-api-access>` for continued access to
+|service|. 
+
+Base Your Script on the Version of the {+atlas-cli+} that You Run
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you create a script to automate processes, you should base the
+script on the version of the {+atlas-cli+} that you currently run.
+**Don't** build automatic upgrades for the {+atlas-cli+} into your
+script because new {+atlas-cli+} releases could introduce breaking
+changes, which could break your automated processes.
+
+Instead, check release notes for deprecated features and
+breaking changes before you manually upgrade your version of the 
+{+atlas-cli+}.
+
+.. _atlas-cli-redirect-stderr:
+
+Redirect ``stderr``
+~~~~~~~~~~~~~~~~~~~
+
+The {+atlas-cli+} prints error messages and command deprecation
+warnings in the output for commands. These unanticipated error messages
+and warnings can cause issues for your automated processes that
+anticipate a specific output. To prevent issues, you can redirect
+``stderr`` to an output file in your script.
+
+For example, the following command redirects the ``stderr`` output from
+a script called ``myScript.sh`` to a text file called ``error.txt``:
+
+.. code-block::
+
+   myScript.sh 2> error.txt
+
+In the previous example, all error messages and deprecation warnings
+are stored in ``error.txt`` and don't display in the output, so
+they don't disrupt your automated processes.
+
+Command deprecation messages are similar to the following text:
+
+.. code-block::
+
+   Command "describe" is deprecated, Please use atlas privateEndpoints aws interfaces describe <atlasPrivateEndpointId> [--privateEndpointId privateEndpointID] [--projectId projected]
+
+Update Scripts Regularly
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+You should regularly update your scripts to discontinue use of 
+deprecated commands because they will be removed in future releases.
+You can learn which commands are deprecated from the
+:ref:`atlas-cli-changelog`. If you 
+:ref:`set up a redirect file for stderr <atlas-cli-redirect-stderr>`,
+you can also check that file for deprecation warnings.
+
+.. toctree::
+   :titlesonly:
+
+   Environment Variables </atlas-cli-env-variables>
+   Customize Output </custom-output-cli>
+