Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edits to Repos Update: Draft guides for integration #6061 #6360

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
+31 −33
Open

Edits to Repos Update: Draft guides for integration #6061 #6360

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
57 changes: 29 additions & 28 deletions advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,60 +1,60 @@
---
title: Using Hosted Artifactory with EDB repositories
title: Using hosted Artifactory with EDB repositories
navTitle: Hosted Artifactory
description: How to use Hosted JFrog Artifactory with EDB repositories
description: How to use hosted JFrog Artifactory with EDB repositories.
---

To set up Hosted JFrog Artifactory with EDB repositories, you need to create remote repositories in Artifactory. This article shows how to use Hosted JFrog Artifactory with EDB repositories. The process is different for on-premises Artifactory.
To set up hosted JFrog Artifactory with EDB repositories, you need to create remote repositories in Artifactory, as described in the procedure that follows. The process is different for on-premises Artifactory.

## Get the base URLs

The process is requires a base URLs to access the EDB repositories.
The process requires that you first get the base URLs to access the EDB repositories.

1. From your EDB account, [get your token](../../getting_started/with_cli/get_your_token).

1. Make a note of your token, for our examples, the token will be `xyz123`.
1. Make a note of your token. For this example, the token is `xyz123`.

1. Select the repository you want to access, for example, `standard`. :
1. Select the repository you want to access, for example, `standard`.

1. Your base URL will is then formed as:
1. Your base URL is then formed as:

```
https://downloads.enterprisedb.com/<token>/<repository>/
```

For the `standard` with our token, the repository, the base URL will be:
For the `standard` repository with the same token, the base URL is:

```
https://downloads.enterprisedb.com/xyz123/standard/
```

1. Append the appropriate path for the repository type.
For example, for a Red Hat Enterprise Linux 9 on x86 architecture, append `rpm/el/9/x86_64/` and seperately append `rpm/el/9/noarch/` for the noarch packages, to create two base URLs. With our example, the base URLs will be:
For example, for a Red Hat Enterprise Linux 9 on x86 architecture, to create the two base URLs, append `rpm/el/9/x86_64/`. Then separately append `rpm/el/9/noarch/` for the `noarch` packages. Using the same example token and repository, the base URLs are:

```
https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/
https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/noarch/
```

## Setup Artifactory remote repositories
## Set up Artifactory remote repositories

With your base URLs, you can now create the remote repositories in Artifactory.
After you have your base URLs, you can create the remote repositories in Artifactory.

Use the Artifactory UI to create the 2 repositories (`x86_64` and `noarch`), one for each base URL. The `x86_64` repository will contain the `rpm` packages specifically for the `x86_64` architecture, and the `noarch` repository will contain the `rpm` packages which are for any architecture.
Use the Artifactory interface to create the two repositories (`x86_64` and `noarch`), one for each base URL. The `x86_64` repository will contain the `rpm` packages specifically for the `x86_64` architecture. The `noarch` repository will contain the `rpm` packages, which are for any architecture.

Starting with the `x86_64` base URL:

1. Select **Create Repository** and choose **Remote**.
1. Choose **rpm** as the repository type.
1. Select **Create Repository > Remote**.
1. Select **rpm** as the repository type.
1. Enter a unique name for the repository key, for example, `edb-x86_64`.
1. Fill in the URL as `https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/`.
1. Enter the `x86_64` base URL, for example, `https://downloads.enterprisedb.com/xyz123/standard/rpm/el/9/x86_64/`.
1. Select **Create Remote Repository**.

At this point, a prompt to setup the `yum` client configuration appears. This client configuration is the configuration you use on your local server or VM to access the configured EDB repositories via Artifactory.
A prompt to set up the yum client configuration appears. This client configuration is the configuration you use on your local server or VM to access the configured EDB repositories via Artifactory.

6. On your local RHEL 9 server or VM create the yum repository file `/etc/yum.repos.d/artifactory-edb.repo`.
1. On your local RHEL 9 server or VM, create the yum repository file `/etc/yum.repos.d/artifactory-edb.repo`.

7. Add the text generated by Artifactory to the `/etc/yum.repos.d/artifactory-edb.repo` file. The generated text should resemble:
1. Add the text generated by Artifactory to the `/etc/yum.repos.d/artifactory-edb.repo` file. The generated text should resemble:

```
[Artifactory]
Expand All @@ -64,9 +64,9 @@ At this point, a prompt to setup the `yum` client configuration appears. This cl
gpgcheck=0
```

Remove the `<PATH_TO_REPODATA_FOLDER>` from the baseurl. It's not needed.
Remove `<PATH_TO_REPODATA_FOLDER>` from the baseurl. It's not needed.

You should also edit the `Artifactory` name to be more descriptive and unique as there are multiple repositories to add. For example, append `-edb-x86_64` to the name to give:
Also edit the name to be more descriptive and unique, as there are multiple repositories to add. For example, append `-edb-x86_64` to the name:

```
[Artifactory-edb-x86_64]
Expand All @@ -78,7 +78,7 @@ At this point, a prompt to setup the `yum` client configuration appears. This cl

Save the file.

8. Repeat the process, steps 1-7, to create an Artifactory remote repository for the `noarch` repository. When you generate the **yum** configuration text, add that text to the `/etc/yum.repos.d/artifactory-edb.repo` file previously created. The file should now contain:
1. Repeat steps 1-7, to create an Artifactory remote repository for the `noarch` repository. After you generate the yum configuration text, add that text to the `/etc/yum.repos.d/artifactory-edb.repo` file you previously created. The file should now contain:

```
[Artifactory-edb-x86_64]
Expand All @@ -94,31 +94,32 @@ At this point, a prompt to setup the `yum` client configuration appears. This cl
gpgcheck=0
```

## Check the configuration works

On the local Linux server where the `/etc/yum.repos.d/artifactory-edb.repo` file resides, check that the repositories configuration is correct by running the following command:
## Check that the configuration works

On the local Linux server where the `/etc/yum.repos.d/artifactory-edb.repo` file resides, check that the repository's configuration is correct by running the following command:

```bash
dnf repolist | grep -i Art
```

The output returned should be:
A correct configuration produces the following output:

```
Artifactory-edb-noarch Artifactory-edb-noarch
Artifactory-edb-x86_64 Artifactory-edb-x86_64
```

As you can see the two repositories are now configured.
This result indicates that the two repositories are configured.

You can now check for a specific package, such as `postgresextended` in the Artifactory repository, using the `dnf list` command.

You can now check for a specific package, such as `postgresextended` in the Artifactory repository, using the `dnf list` command. The package name for this example is `edb-postgresextended15-server` which is EDB Postgres Extended 15. To ensure that you don't get false positives from other repositories, disable all repositories using `--disable-repo=*` and then only enable the `Artifactory-` prefixed repositories using `--enablerepo=Artifactory-*`:
The package name for this example is `edb-postgresextended15-server`, which is EDB Postgres Extended 15. To ensure that you don't get false positives from other repositories, disable all repositories using `--disable-repo=*`, and then enable only the `Artifactory-` prefixed repositories using `--enablerepo=Artifactory-*`:

```bash
dnf list edb-postgresextended15-server --disablerepo=* --enablerepo=Artifactory-*
```

If configured and working correctly the output should resemble:
If the repository is configured and working correctly the output resembles:

```
Updating Subscription Management repositories.
Expand Down
7 changes: 2 additions & 5 deletions advocacy_docs/repos/working_with_repos/integrating/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,13 @@
---
title: Integrating with configuration management tools with EDB repositories
title: Integrating configuration management tools with EDB repositories
navTitle: Integrating
description: How to integrate EDB repositories with configuration management tools
---

In this section, you will find information on how to integrate EDB repositories with configuration management tools.
This section includes information on how to integrate EDB repositories with configuration management tools.

* [Hosted JFrog Artifactory](artifactory)

<br/>
<br/>
<br/>



Loading