Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add More Banner Options to Argocd CR #1605

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

neevnuv
Copy link

@neevnuv neevnuv commented Nov 20, 2024

What type of PR is this?
/kind enhancement

What does this PR do / why we need it:
It add the banner permanent and banner position options to the argocd cr

Have you updated the necessary documentation?

  • Documentation has been updated.
  • Documentation update is required by this PR.

Which issue(s) this PR fixes:
This PR adds an enhancement that allows easily to configure a banner's position and permanence

How to test changes / Special notes to the reviewer:

@neevnuv neevnuv changed the title Add More Banner Options Add More Banner Options to ARGOCD CR Nov 20, 2024
@neevnuv neevnuv changed the title Add More Banner Options to ARGOCD CR Add More Banner Options to Argocd CR Nov 20, 2024
@neevnuv neevnuv marked this pull request as draft November 20, 2024 21:53
@svghadi
Copy link
Collaborator

svghadi commented Nov 21, 2024

Hi @neevnuv , operator supports .spec.extraConfig field which can be used for add extra configs in argocd-cm configmap. Do you think that could be an option for you?
https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#extra-config

We are trying to reduce ArgoCD CRD size so we might deprecate & remove some of the less used fields like .banner in future. Let me know if you find .spec.banner field useful. You can achieve the same result by using .spec.extraConfig.

Example:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
spec:
  extraConfig:
    "ui.bannercontent": "value"
    "ui.bannerurl": "value"
    "ui.bannerpermanent": "value"
    "ui.bannerposition": "value"

@neevnuv
Copy link
Author

neevnuv commented Nov 21, 2024

Hello @svghadi,
Our team uses the .spec.banner option in the Argo cr, but the extraConfig option does also work for us, so we’ll be okay either way.
You may close this issue if the banner field is planned to be deprecated in the future.

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.

2 participants