From 8ba6aad4cbeb929c2bce433d0c21ed18cab4cd6b Mon Sep 17 00:00:00 2001 From: Rowena Date: Mon, 25 Nov 2024 15:42:14 +0100 Subject: [PATCH 1/2] fix(tutorials): batch one --- .../index.mdx | 10 ++-- .../index.mdx | 58 +++++++++---------- .../index.mdx | 9 +-- 3 files changed, 37 insertions(+), 40 deletions(-) diff --git a/tutorials/deploy-hasura-engine-database-postgresql/index.mdx b/tutorials/deploy-hasura-engine-database-postgresql/index.mdx index 0cfdf0a3b9..b2f3a0ee33 100644 --- a/tutorials/deploy-hasura-engine-database-postgresql/index.mdx +++ b/tutorials/deploy-hasura-engine-database-postgresql/index.mdx @@ -10,7 +10,7 @@ categories: - postgresql-and-mysql hero: assets/scaleway_hasura.webp dates: - validation: 2024-05-13 + validation: 2024-11-25 posted: 2020-07-08 --- @@ -37,19 +37,19 @@ Hasura provides a pre-configured [repository](https://github.com/hasura/graphql- 2. Update the `docker-run.sh` script with your PostgreSQL database credentials: - Open the file in a text editor and locate the `HASURA_GRAPHQL_DATABASE_URL` environment variable. Replace `postgres://username:password@hostname:port/dbname` with your database credentials. + Open the file in a text editor and locate the `HASURA_GRAPHQL_DATABASE_URL` environment variable. Replace `postgres://username:password@hostname:port/dbname` with your database credentials. Choose a value for `youradminsecret` that you will use to log into the Hasura console in the next section. ```bash #! /bin/bash docker run -d -p 8080:8080 \ - -e HASURA_GRAPHQL_DATABASE_URL=postgres://youruser:yourpassword@yourhost:5432/yourdatabase \ + -e HASURA_GRAPHQL_DATABASE_URL=postgres://youruser:yourpassword@yourhost:5432/dbname \ -e HASURA_GRAPHQL_ENABLE_CONSOLE=true \ -e HASURA_GRAPHQL_ADMIN_SECRET=youradminsecret \ hasura/graphql-engine:latest ``` - If your database password contains special characters like `@` or `#`, ensure they are [URL-encoded](https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters). + If your database password contains special characters like `@`, `!`, or `#`, ensure they are [URL-encoded](https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters). The default `dbname` is `rdb`. 3. Run the script: @@ -67,7 +67,7 @@ Hasura provides a pre-configured [repository](https://github.com/hasura/graphql- 5. Access the Hasura Console by opening `http://localhost:8080/console` in your browser. You need to use the `HASURA_GRAPHQL_ADMIN_SECRET` value to log in. -### Setting Up Your First Tables and Queries +### Setting Up Your first tables and queries 1. Create tables in the Hasura Console: - Click Data -> Create Table. diff --git a/tutorials/get-started-crossplane-kubernetes/index.mdx b/tutorials/get-started-crossplane-kubernetes/index.mdx index 166c289f7c..6f9aeb2026 100644 --- a/tutorials/get-started-crossplane-kubernetes/index.mdx +++ b/tutorials/get-started-crossplane-kubernetes/index.mdx @@ -9,7 +9,7 @@ tags: crossplane kubernetes categories: - kubernetes dates: - validation: 2024-05-13 + validation: 2024-11-25 posted: 2023-05-05 --- @@ -35,7 +35,7 @@ In this tutorial, you will learn how to install Upbound Universal Crossplane (UX Run the following command to download and install the Upbound `up` command-line interface: ```bash - curl -sL "https://cli.upbound.io/stable/up" | sh + curl -sL "https://cli.upbound.io" | sh sudo mv up /usr/local/bin/ ``` @@ -53,7 +53,7 @@ Run the following `up uxp install` command to install the latest stable version You should see an output like the following: ```plaintext - UXP 1.12.0 installed + UXP 1.18.0-up.1 installed ``` ## Installing the provider into your Kubernetes cluster @@ -101,7 +101,7 @@ Run the following `up uxp install` command to install the latest stable version ``` NAME INSTALLED HEALTHY PACKAGE AGE - provider-scaleway True True xpkg.upbound.io/scaleway/provider-scaleway:v0.1.0 11s + provider-scaleway True True xpkg.upbound.io/scaleway/provider-scaleway:v0..0 11s ``` @@ -116,13 +116,25 @@ Run the following `up uxp install` command to install the latest stable version The provider requires credentials to create and manage Scaleway resources. -1. Run the following command to create a `secret.yaml` file in which your Kubernetes secret configuration will be stored: +1. Run the following command to create a `crossplane-system` [namespace](/containers/container-registry/concepts/#namespace): + + ``` + kubectl create namespace crossplane-system --dry-run=client -o yaml | kubectl apply -f - + ``` + + You should get an output similar to the following: + + ``` + namespace/crossplane-system created + ``` + +2. Run the following command to create a `secret.yaml` file in which your Kubernetes secret configuration will be stored: ``` nano secret.yaml ``` -2. Edit the request payload you will use to create your Kubernetes secret configuration file. Replace the parameters in the following example using the information in the configuration reference table: +3. Edit the request payload you will use in the `secret.yaml` file, to create your Kubernetes secret. Replace the parameters in the following example using the information in the [configuration reference table](#configuration-reference-table-secret-resource): ``` apiVersion: v1 @@ -146,9 +158,9 @@ The provider requires credentials to create and manage Scaleway resources. Secret names must be a valid DNS subdomain, meaning they must consist of lowercase alphanumeric characters, hyphens ("-") or periods and must start and end with an alphanumeric character. Underscores ("_") are not permitted. -3. Paste the content of the request payload and save the changes by following the information displayed on your terminal. +4. Paste the content of the request payload into the contents of the `secret.yaml` file, and save the changes by following the information displayed on your terminal. -4. Run the following command to create the secret previously defined in the secret.yaml file. +5. Run the following command to create the secret you just defined in the `secret.yaml` file. ``` kubectl apply -f secret.yaml @@ -160,18 +172,6 @@ The provider requires credentials to create and manage Scaleway resources. secret/name-of-secret created ``` -5. Run the following command to create a `crossplane-system` [namespace](/containers/container-registry/concepts/#namespace): - - ``` - kubectl create namespace crossplane-system --dry-run=client -o yaml | kubectl apply -f - - ``` - - You should get an output similar to the following: - - ``` - namespace/crossplane-system created - ``` - 6. Run the following command to retrieve details about your secret: ``` @@ -182,7 +182,7 @@ The provider requires credentials to create and manage Scaleway resources. As the information is considered sensitive, the actual secret data will not be returned. -### Configuration reference table +### Configuration reference table - secret resource | Parameter | Description | | :----------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -204,7 +204,7 @@ Create a `.yaml` configuration file to attach your Scaleway credentials to the p nano providerconfig ``` -2. Edit the request payload you will use to create your `providerconfig` file. Replace the parameters in the following example using the information in the configuration reference table: +2. Edit the request payload you will use to create your `providerconfig` file. Replace the parameters in the following example using the information in the [configuration reference table](#configuration-reference-table-providerconfig): ``` apiVersion: scaleway.upbound.io/v1beta1 @@ -213,14 +213,14 @@ Create a `.yaml` configuration file to attach your Scaleway credentials to the p name: default spec: credentials: - source: Secret - secretRef: - name: name-of-secret - namespace: crossplane-system - key: credentials + source: Secret + secretRef: + name: name-of-secret + namespace: crossplane-system + key: credentials ``` -3. Paste the content of the request payload and save the changes by following the information displayed on your terminal. +3. Paste the content of the request payload into the `providerconfig` file, and save the changes by following the information displayed on your terminal. 4. Run the following command to apply the previously set configuration to the secret. Make sure to replace the example file path with your own. @@ -306,7 +306,7 @@ Create a `.yaml` configuration file to attach your Scaleway credentials to the p Events: ``` -### Configuration reference table +### Configuration reference table - providerconfig | Parameter | Description | | :---------- | :----------------------------------------- | diff --git a/tutorials/upgrade-managed-postgresql-database/index.mdx b/tutorials/upgrade-managed-postgresql-database/index.mdx index fac01a78f3..a1677766fa 100644 --- a/tutorials/upgrade-managed-postgresql-database/index.mdx +++ b/tutorials/upgrade-managed-postgresql-database/index.mdx @@ -7,14 +7,11 @@ content: paragraph: This page shows how to upgrade your Database for PostgreSQL to the latest version tags: storage PostgreSQL Database rdb dates: - validation: 2024-05-20 + validation: 2024-11-25 categories: - postgresql-and-mysql --- - - - PostgreSQL version 10 reached its End of Life (EoL) on November 10, 2022. It is **recommended** to upgrade your PostgreSQL database engine to the latest available version as soon as possible. - + [PostgreSQL](https://www.postgresql.org/) is a powerful, open-source object-relational database system with more than 30 years of active development. As major PostgreSQL releases regularly add new features, the layout of the system tables may change. However, the internal data storage format itself rarely changes. This allows you to upgrade a PostgreSQL database system without data loss using the backup and restore functions of the Database API. @@ -46,7 +43,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ 1. Open the [Scaleway console](https://console.scaleway.com) in a web browser and click **Managed Databases** in the **Storage** section of the side menu. The list of your databases displays. -2. Click **+ Create an Instance**. The [Instance creation wizard](https://console.scaleway.com/rdb/instances/create) displays. +2. Click **+ Create a Database Instance**. The [Database Instance creation wizard](https://console.scaleway.com/rdb/instances/create) displays. 3. Select **PostgreSQL-13** from the drop-down list and fill in the [required information](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) for your new database Instance. Then click **Create an Instance**. Your database is created, and you are redirected to the database dashboard. Ensure your new Database Instance is located in the same geographical region as your old one. From 866ccb71c583106ce6545f1751906cce71ce7d7f Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Tue, 26 Nov 2024 10:43:57 +0100 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: nerda-codes <87707325+nerda-codes@users.noreply.github.com> --- tutorials/deploy-hasura-engine-database-postgresql/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/deploy-hasura-engine-database-postgresql/index.mdx b/tutorials/deploy-hasura-engine-database-postgresql/index.mdx index b2f3a0ee33..e7f5c38c65 100644 --- a/tutorials/deploy-hasura-engine-database-postgresql/index.mdx +++ b/tutorials/deploy-hasura-engine-database-postgresql/index.mdx @@ -37,7 +37,7 @@ Hasura provides a pre-configured [repository](https://github.com/hasura/graphql- 2. Update the `docker-run.sh` script with your PostgreSQL database credentials: - Open the file in a text editor and locate the `HASURA_GRAPHQL_DATABASE_URL` environment variable. Replace `postgres://username:password@hostname:port/dbname` with your database credentials. Choose a value for `youradminsecret` that you will use to log into the Hasura console in the next section. + Open the file in a text editor and locate the `HASURA_GRAPHQL_DATABASE_URL` environment variable. Replace `postgres://username:password@hostname:port/dbname` with your database credentials. Choose a value for `youradminsecret` that you will use to log in to the Hasura console in the next section. ```bash #! /bin/bash