If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

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

Hi all 👋

We already released the addon-framework where we want to provide out-of the box integrations with third party tools. It would be super helpful if someone familiar with New Relic could assist on building the New Relic integration. The idea is to inform New Relic about changes via [New Relic Custom events](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-apis/introduct

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.1.0
Also latest master

Liquibase Integration & Version:
gradle, unknown version

Liquibase Extension(s) & Version:

Database Vendor & Version:
PostgreSQL: 12.X (occurs on all supported versions)

Operating System Type & Version:
MacOS 11.4 (20F71), but will occur on all supported OSs

Description

A clear and concis

Summary

Validate Helm Repos as the user adds them.

Motivation

Adding an invalid repo will stop chart deployment as argocd validates all the helm repos before deploying any helm chart.

Proposal

If repo url is : https://helm.devtron.ai/

https://helm.devtron.ai/index.yaml should return a 200 http status

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.