Dan Everton

Logs from the ArgoCD server side: ``` time="2022-05-19T02:54:34Z" level=info msg="received unary call /application.ApplicationService/Create" grpc.method=Create grpc.request.claims="{\"iat\":1652928874,\"iss\":\"argocd\",\"nbf\":1652928874,\"sub\":\"admin\"}" grpc.request.content="%!v(PANIC=String method: reflect.Value.Bytes of non-byte slice)" grpc.request.deadline="2022-05-19T02:59:33Z" grpc.service=application.ApplicationService grpc.start_time="2022-05-19T02:54:34Z" span.kind=server system=grpc ```

Maybe related to https://github.com/spinnaker/orca/pull/4173 as empty changesets should result in the task being successful and moving on to deleting the empty changeset.

@spinnakerbot remove-label stale

@spinnakerbot remove-label stale

Was just thinking about this and wondering if it'd be better to go and create an AWS V2 provider (similar to how the Kubernetes provider migrated)?

@spinnakerbot remove-label stale

I had a very quick look at this and one issue will be that Spinnaker is a bit tied to the Helm 2 `index.yaml` to be able to retrieve the...

We've run a short test of this patch (along with #5375 ) and unfortunately it doesn't seem to fix the issue. We're still seeing a large number of queries in...

The primary way this shows for us is the general search endpoint from the front page of Deck. From a user perspective the search never returns and we see long...

Using the [`TF_IN_AUTOMATION`](https://developer.hashicorp.com/terraform/tutorials/automation/automate-terraform#controlling-terraform-output-in-automation) environment variable removes the init messages and still shows the important information at least. So `TF_IN_AUTOMATION=1 terragrunt run-all apply` is much less verbose.