Skip to content

Commit 7f11306

Browse files
authored
Update some info on distribution servers (ansible#2119)
* update some links * remove galax details and leave it to galaxy docs
1 parent cb1f9d6 commit 7f11306

File tree

1 file changed

+4
-10
lines changed

1 file changed

+4
-10
lines changed

docs/docsite/rst/dev_guide/developing_collections_distributing.rst

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ You must upload your collection into a namespace on each distribution server. If
5757
You can create additional namespaces on Ansible Galaxy if you choose. For Red Hat Automation Hub and private Automation Hub you must create a namespace before you can upload your collection. To create a namespace:
5858

5959
* To create a namespace on Galaxy, see `Galaxy namespaces <https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespaces>`_ on the Galaxy docsite for details.
60-
* To create a namespace on Red Hat Automation Hub, see the `Ansible Certified Content FAQ <https://access.redhat.com/articles/4916901>`_.
60+
* To create a namespace on Red Hat Automation Hub, see the `Red Hat automation content documentation <https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/>`_.
6161

6262
Specify the namespace in the :file:`galaxy.yml` file for each collection. For more information on the :file:`galaxy.yml` file, see :ref:`collections_galaxy_meta`.
6363

@@ -70,8 +70,8 @@ An API token authenticates your connection to each distribution server. You need
7070

7171
To get your API token:
7272

73-
* To get an API token for Galaxy, go to the `Galaxy profile preferences <https://galaxy.ansible.com/me/preferences>`_ page and click :guilabel:`API Key`.
74-
* To get an API token for Automation Hub, go to `the token page <https://cloud.redhat.com/ansible/automation-hub/token/>`_ and click :guilabel:`Load token`.
73+
* To get an API token for Galaxy, see `the Galaxy documentation <https://galaxy.ansible.com/ui/token/>`_.
74+
* To get an API token for Automation Hub, see the `Red Hat automation content documentation <https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/>`_.
7575

7676
.. _galaxy_specify_token:
7777

@@ -389,14 +389,8 @@ The ``ansible-galaxy collection publish`` command triggers an import process, ju
389389
Publishing a collection from the website
390390
----------------------------------------
391391

392-
To publish your collection directly on the Galaxy website:
392+
See the `Galaxy documentation <https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/collections/#via-the-ui>`_ to learn how to publish your collection directly on the Galaxy website.
393393

394-
#. Go to the `My Content <https://galaxy.ansible.com/my-content/namespaces>`_ page, and click the **Add Content** button on one of your namespaces.
395-
#. From the **Add Content** dialog, click **Upload New Collection**, and select the collection archive file from your local filesystem.
396-
397-
When you upload a collection, Ansible always uploads the tarball to the namespace specified in the collection metadata in the ``galaxy.yml`` file, no matter which namespace you select on the website. If you are not an owner of the namespace specified in your collection metadata, the upload request fails.
398-
399-
After Galaxy uploads and accepts a collection, the website shows you the **My Imports** page. This page shows import process information. You can review any errors or warnings about your upload there.
400394

401395
.. seealso::
402396

0 commit comments

Comments
 (0)