redhat-cop / redhat-cop/gitops-catalog

default namespace for ansible automation platform inconsistent

Open
#283 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
383
Forks
184
PR merge metrics
No merged PRs in 30d

Description

Installation AAP operator using the OpenShift console results in install to namespace "aap"

The kustomization here installs to "ansible-automation-platform" namespace.

Is there an established opinion about inconsistencies like this?

Personally I would like to strive to match the defaults. I can do a PR, but I am only just now testing this for the first time today.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the kustomization referenced in the issue and compare its namespace with the Ansible Automation Platform namespace created through the OpenShift console. Check the project’s conventions or maintainer guidance before changing it. Done means the catalog’s namespace matches the agreed default and the installation paths are consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible
Domain
devops, infrastructure
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.