continuous-deployment

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

The Argo CD CLI throws a misleading warning about cluster level privileges when adding a cluster with namespace level privileges.

Only the warning looks wrong, the cluster is

Is it possible to add a check if unleash variable is indeed a json, and disable the option of saving it unless it is?
For example, created a variable for a toggle and selected type to be a json, but I've inserted a string instead of a json and was able to save and pull the value.

{'name': 'test', 'payload': {'type': 'json', 'value': 'not a json'}, 'weightType': 'variable', 'enabled': True}

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

Environment

Liquibase Version: 4.6.1

Liquibase Integration & Version: 4.6.1

Liquibase Extension(s) & Version: 4.6.1

Database Vendor & Version: MySQL8.0.27

Operating System Type & Version: MacOS Monterey 12.0.1

Descript

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.