# Import Elastic DNF/Yum repos into Artifactory

**URL:** <https://discuss.elastic.co/t/import-elastic-dnf-yum-repos-into-artifactory/315375>\
**Category:** Elastic Community and Ecosystem\
**Created:** [September 28, 2022, 1:05pm UTC](https://discuss.elastic.co/t/import-elastic-dnf-yum-repos-into-artifactory/315375 "2022-09-28T13:05:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![UPPERCASE](https://avatars.discourse-cdn.com/v4/letter/u/ee7513/32.png) [@UPPERCASE](https://discuss.elastic.co/u/UPPERCASE)\
**Post date:** [September 28, 2022, 1:05pm UTC](https://discuss.elastic.co/t/import-elastic-dnf-yum-repos-into-artifactory/315375/1 "2022-09-28T13:05:03Z")

</div>

I want to include this repo.

```auto
[elastic-8.x]
name=Elastic repository for 8.x packages
baseurl=https://artifacts.elastic.co/packages/8.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md

```

And this key.

```auto
https://packages.elastic.co/GPG-KEY-elasticsearch

```

However, because the repo is not hosted with directory listing enabled, Artifactory cannot import it. It needs a [repo like CentOS](http://mirror.centos.org/centos/). Arti needs this dir listing so it can retrieve all necessary information to clone the repo, including the key.

Has anyone made this work already? Or is this simply a dead end? Because in that case, I'll just use the regular repo and key, but it's not great performance for large clusters.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 26, 2022, 1:05pm UTC](https://discuss.elastic.co/t/import-elastic-dnf-yum-repos-into-artifactory/315375/2 "2022-10-26T13:05:10Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.