mirror of
https://github.com/fluxcd/flux2.git
synced 2026-02-08 00:37:27 +00:00
0694a9582f
I've noticed during CI, that the current command already expected a configured Docker client to push artifacts to authenticated registries. Some users might not want to have the Docker client in their process (like a CI job) or build an handcrafted config.json file. This would allow this kind of behavior: ``` flux push artifact oci://my-registry.dev/foo:v1 \ --source xxx \ --revision xxx \ --path . \ --creds $TOKEN # Authenticate via "Bearer $TOKEN" Authorization header ``` Or via Autologin: ``` flux push artifact oci://012345678901.dkr.ecr.us-east-1.amazonaws.com/foo:v1 \ --source xxx \ --revision xxx \ --path . \ --provider aws ``` This has been implemented for: * flux push artifact * flux list artifact * flux tag artifact * flux pull artifact This will require another PR in https://github.com/fluxcd/pkg/pull/352 Signed-off-by: Adrien Fillon <adrien.fillon@manomano.com> |
||
|---|---|---|
| .. | ||
| arch.go | ||
| arch_test.go | ||
| crds.go | ||
| crds_test.go | ||
| decryption_provider.go | ||
| decryption_provider_test.go | ||
| ecdsa_curve.go | ||
| ecdsa_curve_test.go | ||
| git_implementation.go | ||
| git_implementation_test.go | ||
| helm_chart_source.go | ||
| helm_chart_source_test.go | ||
| kustomization_source.go | ||
| kustomization_source_test.go | ||
| log_level.go | ||
| log_level_test.go | ||
| public_key_algorithm.go | ||
| public_key_algorithm_test.go | ||
| rsa_key_bits.go | ||
| rsa_key_bits_test.go | ||
| safe_relative_path.go | ||
| safe_relative_path_test.go | ||
| source_bucket_provider.go | ||
| source_bucket_provider_test.go | ||
| source_oci_provider.go | ||