Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

If an invalid token for a local user exists in argocd-secret, the API will refuse to process any request with an error message similar to:

FATA[0002] rpc error: code =

Hi,

It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).

Example

apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
  name: app-remote
  namespace: my-really-really-really-long-ns

k logs po/gitkub

Sorta bad titlte, but I'd love to get a list of all toggles that are responding with 100% yes and are unchanged for the last 30 days. In that case, you can probably delete the toggle as it's not necesarry any more.

In the same vein, also exposing all toggles that has no metrics for the last 30 days would be great for the same use case.

Opening here instead of in unleash-frontend as I want to

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.