# The namespace for the collection used only within the organization

**URL:** <https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896>\
**Category:** Get Help\
**Tags:** collections, galaxy-ng\
**Created:** [December 14, 2023, 6:22am UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896 "2023-12-14T06:22:47Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [December 14, 2023, 6:22am UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/1 "2023-12-14T06:22:47Z")

</div>

Is there a namespace for the collection that will only be used within the organization?

We do not plan to upload any collections to Ansible Galaxy or Automation Hub.  
However, for the purpose of using documentation tools (such as anstibull-docs), we want to treat the roles we have developed as collections. To do this, we need a namespace.

Similar use cases for domain names like `.test.`

- RFC 2606 [RFC 2606 - Reserved Top Level DNS Names](https://datatracker.ietf.org/doc/html/rfc2606)
- RFC 6761 [RFC 6761 - Special-Use Domain Names](https://datatracker.ietf.org/doc/html/rfc6761)

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [December 14, 2023, 6:48am UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/2 "2023-12-14T06:48:33Z")

</div>

A similar question was once asked on the ansible-project mailing list ([https://groups.google.com/g/ansible-project/c/RA7Et95zzsQ/m/gYVihWH-CQAJ](https://groups.google.com/g/ansible-project/c/RA7Et95zzsQ/m/gYVihWH-CQAJ)), unfortunately without any reaction.

Namespaces such as `test` or `private` seem to not yet exist; `local` exists, and is somehow associated to @geerlingguy and @gundalow ([Ansible Galaxy](https://galaxy.ansible.com/ui/namespaces/local/?tab=access)). I hope `local` has been reserved for exactly the purpose that you ask for, but I cannot find it documented anywhere.

---

<div class="post-metadata">

**Author:** ![geerlingguy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/geerlingguy/32/11288_2.png) [@geerlingguy](https://forum.ansible.com/u/geerlingguy)\
**Post date:** [December 14, 2023, 12:42pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/3 "2023-12-14T12:42:53Z")

</div>

Yes, we reserved local precisely for that reason.

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [December 14, 2023, 1:55pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/4 "2023-12-14T13:55:55Z")

</div>

@felixfontein Thank you for the information.

@geerlingguy Thank you. Now then, we will also use the `local` namespace for our organization locally.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [December 14, 2023, 8:44pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/5 "2023-12-14T20:44:17Z")

</div>

I started an attempt to document collection naming, that also includes the `local` namespace: [Document collection naming by felixfontein · Pull Request #987 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/987)

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [December 15, 2023, 12:34am UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/6 "2023-12-15T00:34:22Z")

</div>

Excellent! Thak you.

---

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [December 16, 2023, 6:22pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/7 "2023-12-16T18:22:09Z")

</div>

Could that be extended to `local.*` (regex)? We have several different local collections that we would like to distinguish.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [December 16, 2023, 6:52pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/8 "2023-12-16T18:52:14Z")

</div>

`local` is a namespace, in that you can use every name you want, like `local.foo`, `local.bar`, `local.baz`, `local.bam`, …

---

<div class="post-metadata">

**Author:** ![akira6592](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akira6592/32/222_2.png) [@akira6592](https://forum.ansible.com/u/akira6592)\
**Post date:** [January 3, 2024, 12:35pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/9 "2024-01-03T12:35:32Z")

</div>

I have confirmed that an addition has been made to the section [Naming your collection](https://docs.ansible.com/ansible/devel/dev_guide/developing_collections_creating.html#naming-your-collection) in page Creating collections in the official documentation about `local` namespace.

Thank you!

---

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [January 3, 2024, 1:33pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/10 "2024-01-03T13:33:21Z")

</div>

True. And the `local.*` (regex) namespace reservation ship has already sailed. ([localhappiness](https://galaxy.ansible.com/ui/namespaces/localhappiness/)) That’s okay though. We can live with `local`.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [February 2, 2024, 1:33pm UTC](https://forum.ansible.com/t/the-namespace-for-the-collection-used-only-within-the-organization/2896/11 "2024-02-02T13:33:43Z")

</div>

Closed on February 2, 2024, 1:33pm UTC

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