Noam Gal (old codefresh account)
Noam Gal (old codefresh account)
sorry, linked to the wrong pr
The alternative you supplied is almost identical to the output of the bootstrap. The main difference I can spot at the moment is that the bootstrap also creates an "autopilot-bootstrap"...
yeah, the directory structure you suggest seems like the direction we were thinking. I think that the `projects` folder might also be moved into the `bootstrap//` directory, so at the...
The `repo bootstrap` command does have a `--dry-run` option, which prints to stdout the manifests that are going to be applied to your cluster, and doesn't make any repo changes....
GitHub App is currently not working on the `release-2.0` branch (a fix was merged to `master` yesterday). Once it finds its way to the latest release, we can work on...
I am not sure. I don't know how argo-cd decides which PRs to pick into the current 2.X release. But it seems like a big regression, so I hope it...
great news, thanks for your fix in argo-cd, and input over here.
Your suggestion sounds like the proper way to handle configuration, IMHO. The default behavior should return the complete configuration, the same way `git` views it. I am sure there are...
just to understand the issue - at the moment, autopilot does not do anything provider-specific in *most* cases, unless the user supplies a repoURL for a repository that does not...
Hello @radrad from what i understand, the problem is not in the `bootstrap/argo-cd/kustomization.yaml` file, but in the `bootstrap/argo-cd.yaml` - i would guess that in your repo the `spec.source.path` field has...