* wrapping up team settings / version resolver / requirements APIs in a simpler facade
* add a helper method with tests for resolving a chart name with optional prefix and/or repository to a canonical set of data we can use in version streams / apps framework

Signed-off-by: James Strachan <[email protected]>

so that we can add/delete/update/get apps which map to changing the `jx-apps.yml` instead of the `env/requirements.yaml` file.

this implementation also lets you use helm repo prefixes to fully qualify charts; using the version stream to map prefixes <-> URLs.

e.g. to add flagger/cert manager you can do:

```
jx add app jetstack/cert-manager
jx add app flagger/flagger

```

Signed-off-by: James Strachan <[email protected]>

and reuse the version stream prefixes for repositories in the generated helmfile

also lets add a diff based test case to verify we generate the right helmfile

Signed-off-by: James Strachan <[email protected]>

so that we always use a fixed version in the generated helmfiles

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

so that we can default things like namespace / phase / values.yaml* files across cluster configurations via the Version Stream

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

also ensured we can default the boot phase from the defaults in the version stream

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

to fix lint failure

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

so we use Apps rather than Application to refer to the apps framework and the config for `jx-apps.yml` to avoid confusion

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

as it seems to break lint

Signed-off-by: James Strachan <[email protected]>

to more cleanly differentiate between local chart name and full chart name (with repo prefix)

Signed-off-by: James Strachan <[email protected]>

so that we can give an indication of if we prefer local requirements files (for early stages in boot) versus commands used after boot such as (get|add|upgrade|delete) apps

Signed-off-by: James Strachan <[email protected]>

lets make sure we populate the repository from the team settings/default repo

Signed-off-by: James Strachan <[email protected]>

as we can support full chart names or local chart names; so lets be more specific which name we are using in the code

Signed-off-by: James Strachan <[email protected]>

…file

Signed-off-by: James Strachan <[email protected]>

for remote clusters

Signed-off-by: James Strachan <[email protected]>

which lets us avoid specifying the namespace in remote environments for multi-cluster

Signed-off-by: James Strachan <[email protected]>

#4784

Signed-off-by: James Strachan <[email protected]>

#4784

fixes #4784

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

so they appear nicer when we ask users what provider to use

Signed-off-by: James Strachan <[email protected]>

so folks can try out helmfile and helm 3

Signed-off-by: James Strachan <[email protected]>

as we want to create and manage all k8s resources via helm instead

Signed-off-by: James Strachan <[email protected]>

also add validation of the enviroment variable `JX_SECRETS_YAML` to ensure its defined to point to the secrets yaml file

Signed-off-by: James Strachan <[email protected]>

so that we handle the public chart museum URL and include it into the `jx-apps.yml` file in the pull request

Signed-off-by: James Strachan <[email protected]>

so its easier for folks to populate it. Longer term we can help the user populate it like we do with the current boot approach

rename the `jx-apps.yml` apps.valueFiles to apps.values to match helmfile's naming convention

also allow discovery of a `myrepo/mychart`'s yaml file via `mychart/values.yaml` as using `myrepo/mychart/values.yaml` seems to confuse helm into thinking the `myrepo/mychart` folder is a local chart source code

if we have no releases for a helmfile lets add a dummy empty chart to avoid `helmfile sync` failing in the system or apps dir

refactored the test cases so they are easier to create

lets lazily create the `jx-requirements.values.yaml.gotmpl` file if it does not exist. This lets us use a simpler PR pipeline on local environments without needing to run the whole `jx step verify preinstall` step.

also lets default the `--values` arguments with nice validation if folks don't specify them so we can simplify the OOTB pipelines

which it usually does on helm 2 containers

…pressions

e.g. so we can enable helm 3 in a build pack via `PATH=/opt/bin/helm3-bin:$PATH`

if we are using helmfile for dev

…ues running steps and capturing system out

…amespace#3

if we have configured helm 3 then lets use that version to validate helm

Signed-off-by: James Strachan <[email protected]>

so that we can reuse the same code in jx alpha / jx 3.x where we default to helm 3

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>

Signed-off-by: James Strachan <[email protected]>