Codespell / whitespace fixes

blueprints/apigee/hybrid-gke/ansible/roles/apigee-hybrid/tasks/main.yaml

@@ -105,23 +105,23 @@
 
 - name: Create certificate and private key
   shell: >
-    openssl req  \ 
+    openssl req  \
     -nodes \
     -new \
     -x509 \
     -keyout ~/hybrid-files/certs/server.key \
     -out ~/hybrid-files/certs/server.crt \
-    -subj "/CN=apigee.com' \ 
+    -subj "/CN=apigee.com' \
     -addext "subjectAltName={{ hostnames | map('regex_replace', '^', 'DNS:') | join(',') }}""
     -days 3650
 
-- name: Read certificate 
-  slurp: 
+- name: Read certificate
+  slurp:
     src: ~/hybrid-files/certs/server.crt
   register: certificate_output
 
-- name: Read private ket 
-  slurp: 
+- name: Read private key
+  slurp:
     src: ~/hybrid-files/certs/server.key
   register: privatekey_output
 
@@ -232,10 +232,10 @@
       type: Ready
       status: True
 
-- name: 
+- name:
   kubernetes.core.k8s:
-    state: present   
-    definition: 
+    state: present
+    definition:
       apiVersion: apigee.cloud.google.com/v1alpha1
       kind: ApigeeRoute
       metadata:
@@ -252,12 +252,12 @@
             mode: SIMPLE
         selector:
           app: apigee-ingressgateway
-        enableNonSniClient: true 
+        enableNonSniClient: true
 
 - name: Create google-managed certificate
   kubernetes.core.k8s:
-    state: present   
-    definition: 
+    state: present
+    definition:
       apiVersion: networking.gke.io/v1
       kind: ManagedCertificate
       metadata:
@@ -265,11 +265,11 @@
         namespace: apigee
       spec:
         domains: "{{ hostnames }}"
-      
+
 - name: Create backend config
   kubernetes.core.k8s:
-    state: present  
-    definition:  
+    state: present
+    definition:
       apiVersion: cloud.google.com/v1
       kind: BackendConfig
       metadata:
@@ -330,4 +330,4 @@
           service:
             name: apigee-ingressgateway-hybrid
             port:
-              number: 443    
+              number: 443

blueprints/cloud-operations/network-quota-monitoring/src/plugins/series-firewall-rules.py

@@ -33,7 +33,7 @@ def timeseries(resources):
   # return a single descriptor for network as we don't have limits
   yield MetricDescriptor(f'network/firewall_rules_used',
                          'Firewall rules used per network', ('project', 'name'))
-  # return used/vailable/ratio descriptors for project
+  # return used/available/ratio descriptors for project
   for dtype, name in DESCRIPTOR_ATTRS.items():
     yield MetricDescriptor(f'project/{dtype}', name, ('project',),
                            dtype.endswith('ratio'))

blueprints/data-solutions/bq-ml/demo/README.md

@@ -27,7 +27,7 @@ In this tutorial we will make use of the following main components:
 	- standard: to create a view which contains the model features and the target variable
 	- ML: to train, evaluate and make batch predictions
 - Vertex AI:
-	- Pipeline: to define a configurable and re-usable set of steps to train and evaluate a BQML model
+	- Pipeline: to define a configurable and reusable set of steps to train and evaluate a BQML model
 	- Experiment: to keep track of all the trainings done via the Pipeline
 	- Model Registry: to keep track of the trained versions of a specific model
 	- Endpoint: to serve the model via API
@@ -37,4 +37,4 @@ In this tutorial we will make use of the following main components:
 
 1. Access the Vertex AI Workbench
 2. clone this repository
-2. run the [`bmql_pipeline.ipynb`](bmql_pipeline.ipynb) Jupyter Notebook
+2. run the [`bmql_pipeline.ipynb`](bmql_pipeline.ipynb) Jupyter Notebook

blueprints/data-solutions/bq-ml/demo/bmql_pipeline.ipynb

@@ -435,7 +435,7 @@
     "# Conclusions\n",
     "\n",
     "Thanks to this tutorial we were able to:\n",
-    "- Define a re-usable Vertex AI pipeline to train and evaluate BQ ML models\n",
+    "- Define a reusable Vertex AI pipeline to train and evaluate BQ ML models\n",
     "- Use a Vertex AI Experiment to keep track of multiple trainings for the same model with different parameters (in this case a different split for train/test data)\n",
     "- Deploy the preferred model on a Vertex AI managed Endpoint in order to serve the model for real-time use cases via API\n",
     "- Make batch prediction via Big Query and see what are the top 5 features which influenced the algorithm output"

blueprints/data-solutions/sqlserver-alwayson/scripts/windows-startup-witness.ps1

@@ -22,11 +22,11 @@ $BackupPath = "C:\Backup"
 
 if (-not(Test-Path -Path $InitialSetup -PathType Leaf)) {
   Write-Output "Performing initial setup for witness"
-  
+
   All-Instances-Ready
 
   if (-not(Test-Path -Path $WitnessPath -PathType Container)) {
-    Write-Log "Creatin witness directory $WitnessPath and share..."
+    Write-Log "Creating witness directory $WitnessPath and share..."
     New-Item $WitnessPath -type directory
     New-SmbShare -Name QWitness -Path $WitnessPath -Description "SQL File Share Quorum Witness" -FullAccess ${node_netbios_1}$,${node_netbios_2}$
     Start-Sleep -s 10
@@ -40,7 +40,7 @@ if (-not(Test-Path -Path $InitialSetup -PathType Leaf)) {
   }
 
   icacls $WitnessPath /t /grant '${node_netbios_1}$:(OI)(CI)(M)'
-  icacls $WitnessPath /t /grant '${node_netbios_2}$:(OI)(CI)(M)'  
+  icacls $WitnessPath /t /grant '${node_netbios_2}$:(OI)(CI)(M)'
 
   Cluster-In-Domain
 
@@ -51,4 +51,4 @@ if (-not(Test-Path -Path $InitialSetup -PathType Leaf)) {
 
   New-Item "$WitnessPath\SetupDone.txt"
   New-Item $InitialSetup
-}
+}

blueprints/gke/patterns/autopilot-cluster/README.md

@@ -59,7 +59,7 @@ This blueprint by default deploys an Autopilot cluster with private nodes and pr
 - Use namespaces to restrict access to cluster resources: this blueprint deploys the underlying infrastructure, namespace handling is left to applications.
 
 ### Networking
-- Create a custom mode VPC: this blueprint can optinally deploy a new custom VPC with a single subnet. Otherwise, an existing VPC and subnet can be used.
+- Create a custom mode VPC: this blueprint can optionally deploy a new custom VPC with a single subnet. Otherwise, an existing VPC and subnet can be used.
 - Create a proxy-only subnet: the `vpc_create` variable allows the creation of proxy only subnet, if needed.
 - Configure Shared VPC: by default a new VPC is created within the project, but a Shared VPC can be used when the blueprint handles project creation.
 - Connect the cluster's VPC network to an on-premises network: skipped, out of scope for this blueprint

blueprints/networking/ha-vpn-over-interconnect/README.md

@@ -4,7 +4,7 @@ This blueprint creates a complete HA VPN over Interconnect setup, which leverage
 
 This blueprint supports Dedicated Interconnect and Partner Interconnect.
 
-In case of Partner Interconnect only partial apply is possible at first, which creates the VLAN Attachments. Only once the partner connection is established it is possible to deploy HA VPN Gateway and all dependant resources. 
+In case of Partner Interconnect only partial apply is possible at first, which creates the VLAN Attachments. Only once the partner connection is established it is possible to deploy HA VPN Gateway and all dependent resources.
 
 ## Managed resources and services
 

blueprints/networking/hub-and-spoke-peering/README.md

@@ -1,5 +1,5 @@
 # Hub and spoke via peering VPC architecture
 
-This blueprint was deprecated in the v30.0.0 release, as it's been supersed by the [FAST networking stage](../../../fast/stages/2-networking-a-simple/) that deploys a hub and spoke network via peering (or optionally via VPN), which is regularly updated and can also be deployed as a standalone blueprint.
+This blueprint was deprecated in the v30.0.0 release, as it's been superseded by the [FAST networking stage](../../../fast/stages/2-networking-a-simple/) that deploys a hub and spoke network via peering (or optionally via VPN), which is regularly updated and can also be deployed as a standalone blueprint.
 
 If you still need to access the legacy blueprint, you can check it out using our [v29.0.0 tag](https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/tree/v29.0.0/blueprints/networking/hub-and-spoke-peering).

blueprints/networking/hub-and-spoke-vpn/README.md

@@ -1,5 +1,5 @@
 # Hub and spoke via VPN VPC architecture
 
-This blueprint was deprecated in the v30.0.0 release, as it's been supersed by the [FAST networking stage](../../../fast/stages/2-networking-a-simple/) that deploys a hub and spoke network via VPN (or optionally via peering), which is regularly updated and can also be deployed as a standalone blueprint.
+This blueprint was deprecated in the v30.0.0 release, as it's been superseded by the [FAST networking stage](../../../fast/stages/2-networking-a-simple/) that deploys a hub and spoke network via VPN (or optionally via peering), which is regularly updated and can also be deployed as a standalone blueprint.
 
 If you still need to access the legacy blueprint, you can check it out using our [v29.0.0 tag](https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/tree/v29.0.0/blueprints/networking/hub-and-spoke-vpn).