deploy: 878aa34

Author: mhjacks

blog/2021-12-31-medical-diagnosis/index.html

@@ -1669,7 +1669,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-03-23-acm-mustonlyhave/index.html

@@ -1739,7 +1739,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-03-30-multicloud-gitops/index.html

@@ -1663,7 +1663,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-06-30-ansible-edge-gitops/index.html

@@ -1662,7 +1662,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-07-15-push-vs-pull/index.html

@@ -1663,7 +1663,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-08-24-clustergroups/index.html

@@ -1662,7 +1662,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-09-02-route/index.html

@@ -1739,7 +1739,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-10-12-acm-provisioning/index.html

@@ -1749,7 +1749,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token:

blog/2022-11-20-argo-rollouts/index.html

@@ -1865,7 +1865,7 @@
 Run the following commands:
 $ cp values-secret.yaml.template ~/values-secret.yaml Populate this file with secrets, or credentials, that are needed to deploy the pattern successfully:
 $ vi ~/values-secret.yaml Edit the aws section to refer to the file containing your AWS credentials:
-- name: aws fields: - name: aws_access_key_id ini_file: ~/.aws/credentials ini_key: aws_access_key_id - name: aws_secret_access_key ini_file: ~/.aws/credentials ini_key: aws_secret_access_key - name: baseDomain value: aws.example.com - name: pullSecret path: ~/pull_secret.json - name: ssh-privatekey path: ~/.ssh/privatekey - name: ssh-publickey path: ~/.ssh/publickey Add a Portworx Enterprise DR license:
+- name: aws-creds vaultPrefixes: - global fields: - name: aws_access_key_id value: "" description: "An aws access key that can provision VMs and manage IAM (if using portworx)" - name: aws_secret_access_key value: "" description: "An aws access secret key that can provision VMs and manage IAM (if using portworx)" Add a Portworx Enterprise DR license:
 - name: portworx vaultPrefixes: - global fields: - name: dr_license path: "/path/to/enterprise+dr/license" description: "The portworx dr license that can be activated with \`pxctl license activate saas --key <license>\`" Add the kubeconfigs for both clusters:
 - name: kubeconfigs vaultPrefixes: - global fields: - name: primary_kubeconfig path: "/path/to/primary/cluster/kubeconfig" description: "path to the the kubeconfig for the primary cluster" - name: secondary_kubeconfig path: "/path/to/secondary/cluster/kubeconfig" description: "path to the the kubeconfig for the secondary (failover) cluster" Add an Ansible Automation Platform manifest:
 - name: aap-manifest vaultPrefixes: - hub fields: - name: b64content path: '~/Downloads/<manifest_filename>.zip' base64: true description: "Manifest obtained from following https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/installing_on_openshift_container_platform/assembly-gateway-licensing-operator-copy#assembly-aap-obtain-manifest-files" Add an Ansible Automation Platform Automation Hub token: