- Add provider flag to `flux create source git` command with supported values: azure, generic.
- Unit tests validating the generated yaml and error conditions.
Signed-off-by: Dipti Pai <diptipai89@outlook.com>
The `create source chart` command supports all HelmChart.spec fields
except `.valuesFiles` and `ignoreMissingValuesFiles` as these are
assumingly rarely used fields and the CLI usually only supports
commonly used ones.
closes#4760
Co-authored-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Max Jonas Werner <mail@makk.es>
This makes the pushed artifact have the exact same hash if the contents
are the same.
E.g
```
flux push artifact oci://repo/image:tag1 --source deploy --revision="test" --path=deploy --reproducible
flux push artifact oci://repo/image:tag2 --source deploy --revision="test" --path=deploy --reproducible
```
will both result in the same sha hash, tagged with `tag1` and `tag2`.
This is useful when producing flux artifacts in a monorepo setup where
you don't want to unnecessarily push new artifacts unless something has
actually changed.
Signed-off-by: frekw <fredrik@warnsberg.se>
Allow configuring the list of host key algorithms to use for
SSH connections initialized by the CLI during bootstrap.
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This change introduces two new flags to `create source oci` for
providing the values to the
`OCIRepository.spec.verify.matchOIDCIdentity.(issuer,subject)` fields.
Signed-off-by: Max Jonas Werner <mail@makk.es>
Signed-off-by: toomaj <toomaj@tuta.io>
Set tokenAuth to true with withBearerToken
Signed-off-by: toomaj <toomaj@tuta.io>
Set breaderToken if tokenAuth & withBearerToken were set
Signed-off-by: toomaj <toomaj@tuta.io>
This command can be used to replicate the behavior of the
Flux Kustomization post-build substitutions.
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
Add an optional flag called `--registry-creds` to the bootstrap
command for generating an image pull secret for container images
stored in private registries.
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This can happen when Custom Resource Definitions do not exist on the
cluster. For example, because only a subset of the Flux controllers are
installed on the cluster.
Previously, the detection was based on a combination of error type and
string matching. However, a more reliable (and maintained)
`apimeta.IsNoMatchError` checker is available upstream. Making it less
likely this suddenly stops to matching properly when Kubernetes changes
things.
Signed-off-by: Hidde Beydals <hidde@hhh.computer>
