Open asaf400 opened 1 year ago
Yep. Trying to get some help on this: https://cloud-native.slack.com/archives/C020XM04CUW/p1692801796863639
We have same problem. For example, below way is not working for our environment.
Thanks. https://github.com/argoproj/argo-cd/issues/15184#issuecomment-1690097479
bump
@agaudreault I'm not a maintainer of ArgoCD, we need an org member with high enough privileges, https://cloud-native.slack.com/archives/C020XM04CUW/p1692801796863639
It's quite unprofessional having users to keep going to the old site, and this small issue not fixed, we are all Dev or Ops here,
there's no reason not to devote 5 minutes of a maintainer to unarchive the old repo, make some <div>
heading, deploy the changes and archive again..
or shut down the old site entirely.. 🤷
@crenshaw-dev
This still causes confusion to my teammates. :(
I am happy to help, however the only way to make this change is by an admin of the archived repo.
The fact that ArgoCD maintainers have responded to my duplicate report (closed it), but ignored the contents of it ( DO SOMETHING ABOUT IT ALREADY )
Just enforces my opinion that ArgoCD is an unmaintained mess of a project with no one at the helm, pun intended
This had been opened for more then a year now, simply lovely
PLEASE !
Add a deprecation notice AT THE TOP of the site, at least 15% of the page, that the docs for https://argocd-notifications.readthedocs.io/en/stable/ are for the old and deprecated project argocd-notifications
and that now the features have been implemented and are here: https://argo-cd.readthedocs.io/en/latest/operator-manual/notifications/
any google search for "argocd notifications" gets you to that old doc pages, an unaware user should not go to the github of the project in order to see that it is no longer supported!
P.S I would have created a PR for this, but the repo is archived..