Joshua S

running `atlantis:v0.20.1`, `parallel_plan: true` works for me without locking issues, but i get the below error when trying to run `atlantis apply -d environments/myorg-preprd/preprd`. all environments use the **default** workspace...

i would like to iterate over a yaml list from a git file generator, but i can't get `{{releases}}`, `{{releases[0]}}`, `{{releases.0}}`, etc to render in the below example. ``` apiVersion:...

it looks like the [git file generator flattens the contents of maps/arrays](https://github.com/argoproj/applicationset/blob/de10506d8ff81970567381ef3f4dae4b76f50220/pkg/generators/git_test.go#L369-L409) so basically, ``` apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: abc-values-test spec: generators: - git: repoURL: https://github.com/abc/def revision: HEAD...

imo, https://github.com/tektoncd/pipeline/pull/4176 made defining cpu/mem requests much less intuitive. assuming steps in a task will never run in parallel, task-level resource definition would definitely alleviate some of that pain.

/remove-lifecycle stale we really need an intuitive way to set requests/limits for the entire pod/task

is there a workaround for this in the meantime? even hardcoding the namespace in the `matcher` doesn't work for me: ```yaml apiVersion: monitoring.coreos.com/v1alpha1 kind: AlertmanagerConfig metadata: name: {{ include "thanos-operator.fullname"...

the above was intended to be deployed in my `thanos-operator` chart in the `monitor` namespace. i was reluctant to package a victorops receiver in each application chart and instead wanted...

> I think the issue with this approach would be that it returns tags across multiple branches, where as some of the libraries that rely on `git-semver-tags` assume that it's...

i see 2 existing PRs https://github.com/jenkins-x-plugins/jx-secret/pull/387 https://github.com/jenkins-x-plugins/jx-secret/pull/397 if i were to try and pick this up, which one looks better to start from?

I'm seeing the same issue on an action repo that pushes a `v1` tag as well as the `vx.x.x` semver tag on release