docs: PLT-1948: Palette CLI Breaking Change Updates (Ubuntu Pro) (#8103)

* Updating breaking change re: ubuntu-pro

* Empty commit to trigger Netlify preview

* Splitting ubuntu-pro-token flag into separate PR for backporting

* Update _partials/palette-cli/credentials-breaking-change.mdx

Author: achuribooks

_partials/palette-cli/credentials-breaking-change.mdx

@@ -0,0 +1,10 @@
+---
+partial_category: palette-cli
+partial_name: credentials-breaking-change
+---
+
+Credentials such as Palette API keys, passwords, and Ubuntu Pro tokens set using Palette CLI version 4.7.1 or
+earlier are not compatible with Palette CLI version 4.7.2 or later. As a result, users cannot use configuration files
+created using version 4.7.1 or earlier to perform Palette CLI operations after upgrading to version 4.7.2 or later.
+Refer to our <VersionedLink text="Troubleshooting" url="/troubleshooting/automation#scenario---update-cli-configuration-files-credentials" />
+guide for more information.

docs/docs-content/automation/palette-cli/commands/ec.md

@@ -24,11 +24,7 @@ The `ec` command exposes the following subcommand.
 
 ## Limitations
 
-- Passwords set using Palette CLI version 4.7.1 or earlier are not compatible with Palette CLI version 4.7.2 or later.
-  As a result, users cannot use configuration files created using version 4.7.1 or earlier to perform Palette CLI
-  operations after upgrading to version 4.7.2 or later. Users must update their password by either running the command
-  `palette ec install --config-file <ec-yaml-location> --update-passwords` and completing the subsequent prompts or
-  deleting the existing `ec.yaml` file.
+- <PartialsComponent category="palette-cli" name="credentials-breaking-change" />
 
 ## Prerequisites
 

docs/docs-content/automation/palette-cli/commands/pcg.md

@@ -22,11 +22,7 @@ The `pcg` command exposes the following subcommand.
 
 ## Limitations
 
-- Passwords set using Palette CLI version 4.7.1 or earlier are not compatible with Palette CLI version 4.7.2 or later.
-  As a result, users cannot use configuration files created using version 4.7.1 or earlier to perform Palette CLI
-  operations after upgrading to version 4.7.2 or later. Users must update their password by either running the command
-  `palette pcg install --config-file <pcg-yaml-location> --update-passwords` and completing the subsequent prompts or
-  deleting the existing `pcg.yaml` file.
+- <PartialsComponent category="palette-cli" name="credentials-breaking-change" />
 
 ## Prerequisites
 

docs/docs-content/automation/palette-cli/install-palette-cli.md

@@ -21,10 +21,7 @@ The Palette CLI is available for the following operating systems and architectur
 
 ## Limitations
 
-- Passwords set using Palette CLI version 4.7.1 or earlier are not compatible with Palette CLI version 4.7.2 or later.
-  As a result, users cannot use configuration files created using version 4.7.1 or earlier to perform Palette CLI
-  operations after upgrading to version 4.7.2 or later. Users must update their password by either running the command
-  `palette login --api-key <key>` and completing the subsequent prompts or deleting the existing `palette.yaml` file.
+- <PartialsComponent category="palette-cli" name="credentials-breaking-change" />
 
 ## Prerequisites
 

docs/docs-content/release-notes/release-notes.md

@@ -25,14 +25,12 @@ tags: ["release-notes"]
   using the API should use the `spec.jsonCredentials` field to supply their credentials in JSON format. Refer to the
   [API documentation](/api/introduction) for further details.
 - The previous encryption library used in the [Palette CLI](../automation/palette-cli/palette-cli.md) has been
-  deprecated. As a result, users cannot use their existing configuration files to perform operations after upgrading to
-  Palette CLI version 4.7.2 or later. Users must update their passwords by either running the applicable commands and
-  following the subsequent prompts or deleting the respective configuration files:
-  - [Palette CLI](../automation/palette-cli/install-palette-cli.md) (`palette.yaml`) - `palette login --api-key <key>`
-  - [Enterprise Cluster (EC)](../automation/palette-cli/commands/ec.md) (`ec.yaml`) -
-    `palette ec install --config-file <ec-yaml-location> --update-passwords`
-  - [Private Cloud Gateway (PGC)](../automation/palette-cli/commands/pcg.md) (`pcg.yaml`) -
-    `palette pcg install --config-file <pcg-yaml-location> --update-passwords`
+  deprecated. As a result, users cannot use their existing credentials, such as Palette API keys, passwords, and Ubuntu
+  Pro tokens, to perform operations after upgrading to Palette CLI version 4.7.2 or later. Users must update their
+  credentials by either running the applicable commands and following the subsequent prompts or deleting the respective
+  configuration files. Refer to our
+  [Troubleshooting](../troubleshooting/automation.md#scenario---update-cli-configuration-files-credentials) guide for
+  more information.
 
 #### Features
 

docs/docs-content/troubleshooting/automation.md

@@ -42,6 +42,13 @@ Palette API key, passwords, and other credentials in the CLI configuration files
 due to a changed encryption passphrase or other reasons, you can update the CLI configuration files by using the
 following steps.
 
+:::tip
+
+Alternatively, you can delete the respective `palette.yaml`, `ec.yaml`, or `pcg.yaml` file, and the next time you need
+to perform related Palette CLI operations, you will be prompted to re-enter your credentials.
+
+:::
+
 ### Debug Steps
 
 1.  Log in to the machine where the Palette CLI is installed.
@@ -124,28 +131,3 @@ following steps.
         </TabItem>
 
       </Tabs>
-
-6.  (Optional) Update any previous Palette TC install configuration file that was created using the previous encryption
-    passphrase. You can use the `tc install` command with the `--update-passwords` flag to update the passwords in the
-    configuration. Replace `/path/to/tc.yaml` with the path to the desired TC configuration file. If you are using
-    Ubuntu Pro, pass in the token using the `--ubuntu-pro-token` flag.
-
-    <!-- prettier-ignore -->
-      <Tabs>
-        <TabItem label="Ubuntu Pro Token" value="token">
-
-          ```shell
-          palette tc install --config-file /path/to/tc.yaml --update-passwords --ubuntu-pro-token *************
-          ```
-
-        </TabItem>
-        <!-- prettier-ignore -->
-        <TabItem label="No Ubuntu Pro Token" value="no-token">
-
-          ```shell
-          palette tc install --config-file /path/to/tc.yaml --update-passwords
-          ```
-
-        </TabItem>
-
-      </Tabs>