Skip to content

docs(enterprise-portal): document namespace prop for HelmInstallAssets - #4331

Open
kriscoleman wants to merge 3 commits into
mainfrom
docs/helm-install-assets-namespace
Open

docs(enterprise-portal): document namespace prop for HelmInstallAssets#4331
kriscoleman wants to merge 3 commits into
mainfrom
docs/helm-install-assets-namespace

Conversation

@kriscoleman

@kriscoleman kriscoleman commented Aug 3, 2026

Copy link
Copy Markdown
Member

What

Documents a new optional namespace prop on the <HelmInstallAssets /> component in the Enterprise Portal v2 content reference (docs/vendor/enterprise-portal-v2-content.mdx).

When set, the generated Helm install command includes --namespace <namespace>, so the app installs into that namespace. When omitted, the install uses the default namespace, so existing content is unchanged.

Why

Some customers always install into a fixed namespace. Today the generated command uses the default namespace, so those customers have to hand-edit the copied command every time. The namespace prop lets vendors bake the right namespace straight into the install page and remove that friction.

Examples added

The common case, a single fixed namespace for everyone:

<HelmInstallAssets namespace="my-namespace" />

And an extensible version that defaults to my-namespace but lets a helm_namespace custom license field override it per customer:

<HelmInstallAssets namespace={entitlements.helm_namespace || "my-namespace"} />

Notes

This pairs with the vandoor code PR that adds the namespace prop to <HelmInstallAssets />. The docs shouldn't land ahead of that, so I'm leaving this as a draft until the code side is in.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@netlify

netlify Bot commented Aug 3, 2026

Copy link
Copy Markdown

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 3f1be61
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/6a71548b3cc76100086f687b
😎 Deploy Preview https://deploy-preview-4331--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Aug 3, 2026

Copy link
Copy Markdown

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 3f1be61
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/6a71548be4664e0008b66d46
😎 Deploy Preview https://deploy-preview-4331--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added type::docs Improvements or additions to documentation type::feature labels Aug 3, 2026
Comment thread docs/vendor/enterprise-portal-v2-content.mdx
Comment thread docs/vendor/enterprise-portal-v2-content.mdx
…r name)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@kriscoleman
kriscoleman marked this pull request as ready for review August 4, 2026 01:27
@kriscoleman
kriscoleman requested a review from a team as a code owner August 4, 2026 01:27
@kriscoleman

kriscoleman commented Aug 4, 2026

Copy link
Copy Markdown
Member Author

UAT:
image
image

…ion components

Covers HelmInstallAssets, HelmAirgapInstallAssets, and HelmUpdateAssets after the
prop was extended to be comprehensive/unified across the Helm commands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Comment thread docs/vendor/enterprise-portal-v2-content.mdx
Comment thread docs/vendor/enterprise-portal-v2-content.mdx
@xavpaice

xavpaice commented Aug 4, 2026

Copy link
Copy Markdown
Member

Nits, not blockers:

  • the description inline for the options is substantially more detailed than other options, can we narrow that down to the essential text given that it is explained properly in its own section?
  • there's no --create-namespace, which is fine, but we should probably mention that in the docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants