Skip to content

feat(e2e): add e2e-namespace input to plugin-e2e workflow#166

Open
privilegedescalation-engineer[bot] wants to merge 1 commit intomainfrom
hugh/add-e2e-namespace-input-plugin-e2e
Open

feat(e2e): add e2e-namespace input to plugin-e2e workflow#166
privilegedescalation-engineer[bot] wants to merge 1 commit intomainfrom
hugh/add-e2e-namespace-input-plugin-e2e

Conversation

@privilegedescalation-engineer
Copy link
Copy Markdown
Contributor

Summary

The e2e-namespace input was already documented in caller workflows (e.g. headlamp-sealed-secrets-plugin) but the reusable plugin-e2e.yaml was ignoring it — the namespace was hardcoded to headlamp-dev.

Changes

  • Added e2e-namespace input to plugin-e2e.yaml workflow_call inputs
  • Changed E2E_NAMESPACE job env from hardcoded headlamp-dev to \${{ inputs.e2e-namespace }}

Caller workflows that pass e2e-namespace will now have their value respected.

Testing

  • Existing callers with no e2e-namespace input default to headlamp-dev (backwards compatible)
  • Verified: headlamp-sealed-secrets-plugin/.github/workflows/e2e.yaml passes e2e-namespace: headlamp-dev

Related

  • Observed during PRI-695 RBAC extraction work
  • Fixes namespace input being silently ignored in reusable E2E workflow

The e2e-namespace input was accepted by the reusable workflow but
ignored (namespace was hardcoded to headlamp-dev). Now caller
workflows can specify which namespace to use.

Refs: PRI-695
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant