From b072747abcde28b8e65328a91098381122c25a69 Mon Sep 17 00:00:00 2001 From: Josh Heyer <63653723+josh-heyer@users.noreply.github.com> Date: Tue, 18 May 2021 20:23:01 +0000 Subject: [PATCH 01/14] Fix HTML in titles (hopefully for the last time) Former-commit-id: d57361bb17345ab08fc8a08450a039856b4322d7 --- .../cloud_native_postgresql/api_reference.mdx | 112 +++++++++++++----- 1 file changed, 84 insertions(+), 28 deletions(-) diff --git a/advocacy_docs/kubernetes/cloud_native_postgresql/api_reference.mdx b/advocacy_docs/kubernetes/cloud_native_postgresql/api_reference.mdx index 63209a74331..0173c9dc96c 100644 --- a/advocacy_docs/kubernetes/cloud_native_postgresql/api_reference.mdx +++ b/advocacy_docs/kubernetes/cloud_native_postgresql/api_reference.mdx @@ -51,7 +51,9 @@ Below you will find a description of the defined resources: - [WalBackupConfiguration](#WalBackupConfiguration) -## `AffinityConfiguration` + + +## AffinityConfiguration AffinityConfiguration contains the info we need to create the affinity rules for Pods @@ -61,7 +63,9 @@ Name | Description `topologyKey ` | TopologyKey to use for anti-affinity configuration. See k8s documentation for more info on that - *mandatory* | string `nodeSelector ` | NodeSelector is map of key-value pairs used to define the nodes on which the pods can run. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ | map[string]string -## `Backup` + + +## Backup Backup is the Schema for the backups API @@ -71,7 +75,9 @@ Name | Description `spec ` | Specification of the desired behavior of the backup. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status | [BackupSpec](#BackupSpec) `status ` | Most recently observed status of the backup. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status | [BackupStatus](#BackupStatus) -## `BackupConfiguration` + + +## BackupConfiguration BackupConfiguration defines how the backup of the cluster are taken. Currently the only supported backup method is barmanObjectStore. For details and examples refer to the Backup and Recovery section of the documentation @@ -79,7 +85,9 @@ Name | Description | Type ----------------- | ------------------------------------------------- | ------------------------------------------------------------------ `barmanObjectStore` | The configuration for the barman-cloud tool suite | [*BarmanObjectStoreConfiguration](#BarmanObjectStoreConfiguration) -## `BackupList` + + +## BackupList BackupList contains a list of Backup @@ -88,7 +96,9 @@ Name | Description `metadata` | Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) `items ` | List of backups - *mandatory* | [[]Backup](#Backup) -## `BackupSpec` + + +## BackupSpec BackupSpec defines the desired state of Backup @@ -96,7 +106,9 @@ Name | Description | Type ------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------- `cluster` | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) -## `BackupStatus` + + +## BackupStatus BackupStatus defines the observed state of Backup @@ -115,7 +127,9 @@ Name | Description `commandOutput ` | The backup command output | string `commandError ` | The backup command output | string -## `BarmanObjectStoreConfiguration` + + +## BarmanObjectStoreConfiguration BarmanObjectStoreConfiguration contains the backup configuration using Barman against an S3-compatible object storage @@ -128,7 +142,9 @@ Name | Description `wal ` | The configuration for the backup of the WAL stream. When not defined, WAL files will be stored uncompressed and may be unencrypted in the object store, according to the bucket default policy. | [*WalBackupConfiguration](#WalBackupConfiguration) `data ` | The configuration to be used to backup the data files When not defined, base backups files will be stored uncompressed and may be unencrypted in the object store, according to the bucket default policy. | [*DataBackupConfiguration](#DataBackupConfiguration) -## `BootstrapConfiguration` + + +## BootstrapConfiguration BootstrapConfiguration contains information about how to create the PostgreSQL cluster. Only a single bootstrap method can be defined among the supported ones. `initdb` will be used as the bootstrap method if left unspecified. Refer to the Bootstrap page of the documentation for more information. @@ -137,7 +153,9 @@ Name | Description | Type `initdb ` | Bootstrap the cluster via initdb | [*BootstrapInitDB](#BootstrapInitDB) `recovery` | Bootstrap the cluster from a backup | [*BootstrapRecovery](#BootstrapRecovery) -## `BootstrapInitDB` + + +## BootstrapInitDB BootstrapInitDB is the configuration of the bootstrap process when initdb is used Refer to the Bootstrap page of the documentation for more information. @@ -149,7 +167,9 @@ Name | Description `redwood ` | If we need to enable/disable Redwood compatibility. Requires EPAS and for EPAS defaults to true | *bool `options ` | The list of options that must be passed to initdb when creating the cluster | []string -## `BootstrapRecovery` + + +## BootstrapRecovery BootstrapRecovery contains the configuration required to restore the backup with the specified name and, after having changed the password with the one chosen for the superuser, will use it to bootstrap a full cluster cloning all the instances from the restored primary. Refer to the Bootstrap page of the documentation for more information. @@ -158,7 +178,9 @@ Name | Description `backup ` | The backup we need to restore - *mandatory* | [corev1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) `recoveryTarget` | By default the recovery will end as soon as a consistent state is reached: in this case that means at the end of a backup. This option allows to fine tune the recovery process | [*RecoveryTarget](#RecoveryTarget) -## `Cluster` + + +## Cluster Cluster is the Schema for the PostgreSQL API @@ -168,7 +190,9 @@ Name | Description `spec ` | Specification of the desired behavior of the cluster. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status | [ClusterSpec](#ClusterSpec) `status ` | Most recently observed status of the cluster. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status | [ClusterStatus](#ClusterStatus) -## `ClusterList` + + +## ClusterList ClusterList contains a list of Cluster @@ -177,7 +201,9 @@ Name | Description `metadata` | Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) `items ` | List of clusters - *mandatory* | [[]Cluster](#Cluster) -## `ClusterSpec` + + +## ClusterSpec ClusterSpec defines the desired state of Cluster @@ -205,7 +231,9 @@ Name | Description `licenseKey ` | The license key of the cluster. When empty, the cluster operates in trial mode and after the expiry date (default 30 days) the operator will cease any reconciliation attempt. For details, please refer to the license agreement that comes with the operator. | string `monitoring ` | The configuration of the monitoring infrastructure of this cluster | [*MonitoringConfiguration](#MonitoringConfiguration) -## `ClusterStatus` + + +## ClusterStatus ClusterStatus defines the observed state of Cluster @@ -228,7 +256,9 @@ Name | Description `phaseReason ` | Reason for the current phase | string `secretsResourceVersion` | The list of resource versions of the secrets managed by the operator. Every change here is done in the interest of the instance manager, which will refresh the secret data | [SecretsResourceVersion](#SecretsResourceVersion) -## `DataBackupConfiguration` + + +## DataBackupConfiguration DataBackupConfiguration is the configuration of the backup of the data directory @@ -239,7 +269,9 @@ Name | Description `immediateCheckpoint` | Control whether the I/O workload for the backup initial checkpoint will be limited, according to the `checkpoint_completion_target` setting on the PostgreSQL server. If set to true, an immediate checkpoint will be used, meaning PostgreSQL will complete the checkpoint as soon as possible. `false` by default. | bool `jobs ` | The number of parallel jobs to be used to upload the backup, defaults to 2 | *int32 -## `MonitoringConfiguration` + + +## MonitoringConfiguration MonitoringConfiguration is the type containing all the monitoring configuration for a certain cluster @@ -248,7 +280,9 @@ Name | Description | `customQueriesConfigMap` | The list of config maps containing the custom queries | [[]corev1.ConfigMapKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#configmapkeyselector-v1-core) `customQueriesSecret ` | The list of secrets containing the custom queries | [[]corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) -## `NodeMaintenanceWindow` + + +## NodeMaintenanceWindow NodeMaintenanceWindow contains information that the operator will use while upgrading the underlying node. @@ -259,7 +293,9 @@ Name | Description `inProgress` | Is there a node maintenance activity in progress? - *mandatory* | bool `reusePVC ` | Reuse the existing PVC (wait for the node to come up again) or not (recreate it elsewhere) - *mandatory* | *bool -## `PostgresConfiguration` + + +## PostgresConfiguration PostgresConfiguration defines the PostgreSQL configuration @@ -268,7 +304,9 @@ Name | Description `parameters` | PostgreSQL configuration options (postgresql.conf) | map[string]string `pg_hba ` | PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file) | []string -## `RecoveryTarget` + + +## RecoveryTarget RecoveryTarget allows to configure the moment where the recovery process will stop. All the target options except TargetTLI are mutually exclusive. @@ -282,7 +320,9 @@ Name | Description `targetImmediate` | End recovery as soon as a consistent state is reached | *bool `exclusive ` | Set the target to be exclusive (defaults to true) | *bool -## `RollingUpdateStatus` + + +## RollingUpdateStatus RollingUpdateStatus contains the information about an instance which is being updated @@ -291,7 +331,9 @@ Name | Description | Type `imageName` | The image which we put into the Pod - *mandatory* | string `startedAt` | When the update has been started | [metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) -## `S3Credentials` + + +## S3Credentials S3Credentials is the type for the credentials to be used to upload files to S3 @@ -300,7 +342,9 @@ Name | Description | Type `accessKeyId ` | The reference to the access key id - *mandatory* | [corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) `secretAccessKey` | The reference to the secret access key - *mandatory* | [corev1.SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#secretkeyselector-v1-core) -## `ScheduledBackup` + + +## ScheduledBackup ScheduledBackup is the Schema for the scheduledbackups API @@ -310,7 +354,9 @@ Name | Description `spec ` | Specification of the desired behavior of the ScheduledBackup. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status | [ScheduledBackupSpec](#ScheduledBackupSpec) `status ` | Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status | [ScheduledBackupStatus](#ScheduledBackupStatus) -## `ScheduledBackupList` + + +## ScheduledBackupList ScheduledBackupList contains a list of ScheduledBackup @@ -319,7 +365,9 @@ Name | Description `metadata` | Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds | [metav1.ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#listmeta-v1-meta) `items ` | List of clusters - *mandatory* | [[]ScheduledBackup](#ScheduledBackup) -## `ScheduledBackupSpec` + + +## ScheduledBackupSpec ScheduledBackupSpec defines the desired state of ScheduledBackup @@ -329,7 +377,9 @@ Name | Description `schedule` | The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron. - *mandatory* | string `cluster ` | The cluster to backup | [v1.LocalObjectReference](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#localobjectreference-v1-core) -## `ScheduledBackupStatus` + + +## ScheduledBackupStatus ScheduledBackupStatus defines the observed state of ScheduledBackup @@ -339,7 +389,9 @@ Name | Description `lastScheduleTime` | Information when was the last time that backup was successfully scheduled. | [*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) `nextScheduleTime` | Next time we will run a backup | [*metav1.Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#time-v1-meta) -## `SecretsResourceVersion` + + +## SecretsResourceVersion SecretsResourceVersion is the resource versions of the secrets managed by the operator @@ -351,7 +403,9 @@ Name | Description `caSecretVersion ` | The resource version of the "ca" secret version - *mandatory* | string `serverSecretVersion ` | The resource version of the PostgreSQL server-side secret version - *mandatory* | string -## `StorageConfiguration` + + +## StorageConfiguration StorageConfiguration is the configuration of the storage of the PostgreSQL instances @@ -362,7 +416,9 @@ Name | Description `resizeInUseVolumes` | Resize existent PVCs, defaults to true | *bool `pvcTemplate ` | Template to be used to generate the Persistent Volume Claim | [*corev1.PersistentVolumeClaimSpec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#persistentvolumeclaim-v1-core) -## `WalBackupConfiguration` + + +## WalBackupConfiguration WalBackupConfiguration is the configuration of the backup of the WAL stream From 59b7d3a34f8f2b6d530f69d76f24b95e796e72ad Mon Sep 17 00:00:00 2001 From: sheetal Date: Wed, 19 May 2021 10:42:06 +0530 Subject: [PATCH 02/14] DB-1232 Installation guides needs update for new parameter ' repo_gpgcheck = 1' in new edb.repo rpm file Former-commit-id: 3cbfe623f98d0fe5b7e74e7eae04987c67acdb1d --- ...age_manager_to_install_advanced_server.mdx | 57 +++---------------- .../epas/13/edb_pgadmin_linux_qs/index.mdx | 4 +- ...age_manager_to_install_advanced_server.mdx | 55 +++--------------- ...06_installing_and_configuring_pgadmin4.mdx | 11 +--- .../docs/epas/13/epas_qs_linux_7/index.mdx | 2 +- .../docs/epas/13/epas_qs_linux_8/index.mdx | 2 +- 6 files changed, 24 insertions(+), 107 deletions(-) diff --git a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index f3d22bab6ea..7e4ffb99951 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -140,22 +140,9 @@ You can use an RPM package to install Advanced Server on a CentOS host. dnf -qy module disable postgresql ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -After creating the `edb.repo` file, use your choice of editor to set the value of the `enabled` parameter to `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with a registered EnterpriseDB username and password. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -After saving your changes to the configuration file, you must download and install the repository keys: - -Use the following command to download the repository key. Provide the registered `username` and `password` with the `curl` command to download the key. +You must download and install the repository key. Provide the registered `username` and `password` with the `curl` command to download the repository key using the following command: ```text curl -o /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY https://:@yum.enterprisedb.com/ENTERPRISEDB-GPG-KEY @@ -252,22 +239,9 @@ You can use an RPM package to install Advanced Server on a RHEL host. dnf -qy module disable postgresql ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` - -After creating the `edb.repo` file, use your choice of editor to set the value of the `enabled` parameter to `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with a registered EnterpriseDB username and password. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -After saving your changes to the configuration file, you must download and install the repository keys: +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -Use the following command to download the repository key. Provide the registered `username` and `password` with the `curl` command to download the key. +You must download and install the repository key. Provide the registered `username` and `password` with the `curl` command to download the repository key using the following command: ```text curl -o /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY https://:@yum.enterprisedb.com/ENTERPRISEDB-GPG-KEY @@ -312,7 +286,7 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 The repository configuration file is named `advance-toolchain.repo`. The file resides in `/etc/yum.repos.d.` -- After creating the ` advance-toolchain.repo` file, use your choice of editor to set the value of the `enabled` parameter to `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with a registered EnterpriseDB username and password. +- After creating the `advance-toolchain.repo` file, the `enabled` parameter is set to `1` by default. ```text [advance-toolchain] @@ -331,7 +305,7 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -- Replace the `USERNAME:PASSWORD` placeholder in the following command with the username and password of a registered EnterpriseDB user: +- Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EnterpriseDB user: ```text sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo @@ -353,22 +327,9 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` - - After creating the `edb.repo` file, use your choice of editor to set the value of the `enabled` parameter to `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with a registered EnterpriseDB username and password. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -After saving your changes to the configuration file, you must download and install the repository keys: +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -Use the following command to download the repository key. Provide the registered `username` and `password` with the `curl` command to download the key. +You must download and install the repository key. Provide the registered `username` and `password` with the `curl` command to download the repository key using the following command: ```text curl -o /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY https://:@yum.enterprisedb.com/ENTERPRISEDB-GPG-KEY @@ -865,7 +826,7 @@ The following steps will walk you through using the EnterpriseDB apt repository apt-get -y install apt-transport-https ``` -- Add the EBD signing key: +- Add the EDB signing key: ```text wget -q -O - https://apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - diff --git a/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx b/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx index 972d38edb0c..3f65778bdba 100644 --- a/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx +++ b/product_docs/docs/epas/13/edb_pgadmin_linux_qs/index.mdx @@ -14,7 +14,7 @@ You can use the following steps to use the yum package manager to install EDB pg **Create a Repository Configuration File** -To create a repository configuration file, you must have the credentials that allow to access the EnterpriseDB repository. For information about requesting credentials, visit: +To create a repository configuration file, you must have the credentials that allow access to the EDB repository. For information about requesting credentials, visit: . @@ -24,7 +24,7 @@ To create the repository configuration file, assume superuser privileges and inv yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the `baseurl` specification with the username and password of a registered EDB user: +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the baseurl specification with the username and password of a registered EDB user: ```text sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 3203d213400..ab7f94bf111 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -139,22 +139,9 @@ You can use an RPM package to install Advanced Server on a CentOS host. dnf -qy module disable postgresql ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -After creating the `edb.repo` file, the `enabled` parameter is set to `1` by default. Replace the `username` and `password` placeholders in the `baseurl` specification with the registered EDB username and password. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -After saving your changes to the configuration file, you must download and install the repository keys: - -Use the following command to download the repository key. Provide the registered `username` and `password` with the `curl` command to download the key. +You must download and install the repository key. Provide the registered `username` and `password` with the `curl` command to download the repository key using the following command: ```text curl -o /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY https://:@yum.enterprisedb.com/ENTERPRISEDB-GPG-KEY @@ -251,22 +238,9 @@ You can use an RPM package to install Advanced Server on a RHEL host. dnf -qy module disable postgresql ``` -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` - -After creating the `edb.repo` file, the `enabled` parameter is set to `1` by default. Replace the `username` and `password` placeholders in the `baseurl` specification with the registered EDB username and password. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -After saving your changes to the configuration file, you must download and install the repository keys: +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -Use the following command to download the repository key. Provide the registered `username` and `password` with the `curl` command to download the key. +You must download and install the repository key. Provide the registered `username` and `password` with the `curl` command to download the repository key using the following command: ```text curl -o /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY https://:@yum.enterprisedb.com/ENTERPRISEDB-GPG-KEY @@ -334,7 +308,7 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -- Replace the `USERNAME:PASSWORD` placeholder in the following command with the username and password of a registered EDB user: +- Replace the `USERNAME:PASSWORD` variable in the following command with the username and password of a registered EDB user: ```text sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo @@ -358,22 +332,9 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` - The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` - - After creating the `edb.repo` file, the `enabled` parameter is set to `1` by default. Replace the `username` and `password` placeholders in the `baseurl` specification with the registered EDB username and password. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -After saving your changes to the configuration file, you must download and install the repository keys: +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -Use the following command to download the repository key. Provide the registered `username` and `password` with the `curl` command to download the key. +You must download and install the repository key. Provide the registered `username` and `password` with the `curl` command to download the repository key using the following command: ```text curl -o /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY https://:@yum.enterprisedb.com/ENTERPRISEDB-GPG-KEY @@ -576,7 +537,7 @@ The following steps will walk you through using the EDB apt repository to instal apt-get -y install apt-transport-https ``` -- Add the EBD signing key: +- Add the EDB signing key: ```text wget -q -O - https://apt.enterprisedb.com/edb-deb.gpg.key | sudo apt-key add - diff --git a/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx b/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx index 5f55f0aa2ee..c721a4b791b 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx @@ -20,7 +20,7 @@ You can use the following steps to install pgAdmin4 using `yum` package manager: **Create a Repository Configuration File** -To create a repository configuration file, you must have the credentials that allow to access the EDB repository. For information about requesting credentials, visit: +To create a repository configuration file, you must have the credentials that allow access to the EDB repository. For information about requesting credentials, visit: @@ -32,15 +32,10 @@ yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d.` -After creating the `edb.repo` file, the `enabled` parameter is set to `1` by default. Replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. +After creating the `edb.repo` file, use the following command to replace the `USERNAME` and `PASSWORD` placeholders in the baseurl specification with the username and password of a registered EDB user: ```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` !!! Note diff --git a/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx b/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx index c8d57ea7235..68846e93911 100644 --- a/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx +++ b/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx @@ -54,7 +54,7 @@ yum -y install java yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -**Step 3:** With your choice of editor, edit the `/etc/yum.repos.d/edb.repo` file, replacing the `username` and `password` placeholders in the baseurl specification with the name and password of a registered EDB user and ensure that the `gpgcheck` and `enabled` properties are set to `1`. +**Step 3:** With your choice of editor, edit the `/etc/yum.repos.d/edb.repo` file, replacing the `username` and `password` placeholders in the baseurl specification with the name and password of a registered EDB user. **Step 4:** Update the cache and install Advanced Server: diff --git a/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx b/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx index 5d11ff62ade..f71656feaa4 100644 --- a/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx +++ b/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx @@ -54,7 +54,7 @@ dnf -y install java dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -**Step 3:** With your choice of editor, edit the `/etc/yum.repos.d/edb.repo` file, replacing the `username` and `password` placeholders in the baseurl specification with the name and password of a registered EDB user and ensure that the `gpgcheck` and `enabled` properties are set to `1`. +**Step 3:** With your choice of editor, edit the `/etc/yum.repos.d/edb.repo` file, replacing the `username` and `password` placeholders in the baseurl specification with the name and password of a registered EDB user. **Step 4:** Update the cache and install Advanced Server: From fd79f036791074fc4b91f9a3a33d946c6659b6b0 Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 11:51:31 +0530 Subject: [PATCH 03/14] Updates for DF-229: JDBC 42.2.12.3 Former-commit-id: 9316ec373926f11b47c96416786bcf4b72bc4588 --- .../01_installing_the_connector_with_an_rpm_package.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 76c621545ba..f7c3a3e7ff9 100644 --- a/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -63,6 +63,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -127,6 +128,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -187,6 +189,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -250,6 +253,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` From a2ccdb0e9e613c60c8f7d87511351277b2ea57d6 Mon Sep 17 00:00:00 2001 From: josh-heyer Date: Wed, 19 May 2021 07:59:56 +0000 Subject: [PATCH 04/14] New PDFs generated by Github Actions Former-commit-id: 74a1a8c047bdc9a1ab97609ef14ae857debe11eb From e71e5cd6462bdd3bc43ca46364d9a195a803fa5a Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 14:25:36 +0530 Subject: [PATCH 05/14] Updates for DF-229 Former-commit-id: 92b126684a850fc813b2ed68c5b63c8140dc41a2 --- .../01_installing_the_connector_with_an_rpm_package.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 76c621545ba..f7c3a3e7ff9 100644 --- a/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -63,6 +63,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -127,6 +128,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -187,6 +189,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -250,6 +253,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` From 52a8d6c514ec665554129964967a2b73915105b4 Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 15:51:16 +0530 Subject: [PATCH 06/14] Updates for DF-229: ODBC 12.2.0.2 Former-commit-id: 4fffddb86478b047656964e471c6ce51e256dd26 --- .../12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index 8da37afa14f..a05fb787f9f 100644 --- a/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -65,6 +65,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -131,6 +132,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -193,6 +195,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -258,6 +261,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` From c5b3178cf3cb8c6891a2370d825152cc1f4f21d5 Mon Sep 17 00:00:00 2001 From: josh-heyer Date: Wed, 19 May 2021 10:42:40 +0000 Subject: [PATCH 07/14] New PDFs generated by Github Actions Former-commit-id: 40ddc298f09ddf248650e7007a68471c54584b2e From 91675f56a8b467e3c8a9b9e3c2cbcb0e50df26d0 Mon Sep 17 00:00:00 2001 From: Manjusha Vaidya Date: Wed, 19 May 2021 16:20:55 +0530 Subject: [PATCH 08/14] Added_note Former-commit-id: 0cb31b972d9434307d58da809cef156f0bdbf8f8 --- product_docs/docs/postgis/1.0/01_installing_postgis.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/postgis/1.0/01_installing_postgis.mdx b/product_docs/docs/postgis/1.0/01_installing_postgis.mdx index 5a2c0993fa4..3f2e8671b75 100644 --- a/product_docs/docs/postgis/1.0/01_installing_postgis.mdx +++ b/product_docs/docs/postgis/1.0/01_installing_postgis.mdx @@ -476,8 +476,12 @@ You can use the Zypper package manager to install PostGIS on a SLES 12 host. Zyp ## Installing PostGIS on a Windows Host -You must install Advanced Server before installing PostGIS. If you have used the graphical Setup wizard to install Advanced Server, you can use StackBuilder Plus to add PostGIS to your installation. For details about using the graphical installer to install and configure Advanced Server, see the EDB Advanced Server Installation Guide for Windows. +You must install Advanced Server before installing PostGIS. If you have used the graphical Setup wizard to install EDB Postgres Advanced Server, you can use StackBuilder Plus to add PostGIS to your installation. For details about using the graphical installer to install and configure Advanced Server, see the EDB Postgres Advanced Server Installation Guide for Windows. +!!! Note + + To install PostGIS version 3.1 on EDB Postgres Advanced Server version 9.6 or 10 on Windows, you need to upgrade it to the latest EDB Postgres Advanced Server minor version of 9.6.21.28 or 10.16.25 (or later), and then proceed with PostGIS 3.1 installation. + 1. Open StackBuilder Plus and select your Advanced Server installation from the drop-down list on the `Welcome` window. Click `Next` to continue to the application selection page. ![The StackBuilder Plus Welcome window](images/SBP_welcome.png) From 4d81ab494e7a42f4a3877176de796023fff0c45c Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 17:00:35 +0530 Subject: [PATCH 09/14] Updates for DF-229: ODBC 12.0.0.2 Former-commit-id: 26fd63130ff34c4560dba908db3bda88a2c0e40c --- .../12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index cf23514714e..009183e666c 100644 --- a/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -68,6 +68,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` From 7a2602c78c5fa45a974450ebbe97bd779fe05790 Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 17:07:30 +0530 Subject: [PATCH 10/14] Updates for DF-229: OCL 12.1.2.1 Former-commit-id: ad4409ea5018f4a657d0b71fcdfd218c1ec89961 --- .../01_installing_and_configuring_the_ocl_connector.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index c49c9e4eee0..d33e7692401 100644 --- a/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -63,6 +63,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -129,6 +130,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -191,6 +193,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -256,6 +259,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` From 89881ffe27a81a7ac30c1631682c74c25abdbc21 Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 17:13:02 +0530 Subject: [PATCH 11/14] Updates for DF-229: OCL 13.1.4.2 Former-commit-id: 76ebd9f5cbded66491324657407974ddafceaebc --- .../01_installing_and_configuring_the_ocl_connector.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index e1239439109..527ed316098 100644 --- a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -67,6 +67,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -133,6 +134,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -195,6 +197,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` @@ -260,6 +263,7 @@ name=EnterpriseDB RPMs $releasever - $basearch baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch enabled=1 gpgcheck=1 +repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` From 0de5901cc549d3c1d27ef41d11cacfc698a0759e Mon Sep 17 00:00:00 2001 From: Abhilasha Narendra Date: Wed, 19 May 2021 18:04:46 +0530 Subject: [PATCH 12/14] Fixed alignment Former-commit-id: 8dd40320ab8f9d2b94946da94d36f88f16c7ecd9 --- .../01_installing_and_configuring_the_ocl_connector.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index 527ed316098..5b019d3a2f4 100644 --- a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -51,9 +51,9 @@ After receiving your repository credentials you can: To create the repository configuration file, assume superuser privileges, and invoke the following command: -> ```text -> yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -> ``` + ```text + yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. From d0c0ea3fed97ce8467b6b17fef89374cd1cd291f Mon Sep 17 00:00:00 2001 From: josh-heyer Date: Wed, 19 May 2021 12:45:48 +0000 Subject: [PATCH 13/14] New PDFs generated by Github Actions Former-commit-id: 747e9bf465a0bd6dcbf541c40ce8c38df8092f64 From 27d4a95b8f1b0871df1df696d782412b4547a3ae Mon Sep 17 00:00:00 2001 From: josh-heyer Date: Wed, 19 May 2021 14:07:04 +0000 Subject: [PATCH 14/14] New PDFs generated by Github Actions Former-commit-id: 042cbedad795233d007028a26ea671626d5d1381