---
title: "Discussion on \"Why We Killed Nested Namespaces (And You Probably Should Too)\" | Hashnode"
description: "Discussion on \"Why We Killed Nested Namespaces (And You Probably Should Too)\". The Plan vs. Reality\nAfter fixing our wildcard policy disaster, we thought we were done. We weren't.\nThe real problem was our namespace architecture. We'd designed this beautiful parent-child hierarchy:\nengineering/\n  ├── team-alpha/\n  ├── team-beta/..."
url: "https://hashnode.com/posts/why-we-killed-nested-namespaces-and-you-probably-should-too/697c138f516787686aeb584f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why We Killed Nested Namespaces (And You Probably Should Too)](https://hashiworld.hashnode.dev/why-we-killed-nested-namespaces-and-you-probably-should-too?utm_source=hashnode&utm_medium=feed)

The Plan vs. Reality After fixing our wildcard policy disaster, we thought we were done. We weren't. The real problem was our namespace architecture. We'd designed this beautiful parent-child hierarchy: engineering/ ├── team-alpha/ ├── team-beta/...

Jan 30 · 3 min read · hashiworld.hashnode.dev  
Read the article

-   [#hashicorp](https://hashnode.com/tag/hashicorp)
-   [#terraform](https://hashnode.com/tag/terraform)
-   [#vault](https://hashnode.com/tag/vault)
-   [#yaml](https://hashnode.com/tag/yaml)

## Written by

[Bhanu prakash](https://hashnode.com/@bhanu9398)

@bhanu9398

  
[View profile](https://hashnode.com/@bhanu9398)

DevOps Engineer

DevOps Engineer specializing in HashiCorp Vault, Red Hat Ansible, and cloud infrastructure. Writing about real-world secrets management, automation, and enterprise DevOps at scale.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
