Stefan Prodan

There is no SSH here, you need to give bootstrap the http address and --token-auth.

This is how it works for HTTP and basic auth: ``` flux bootstrap git -s --allow-insecure-http=true --token-auth \ --url=http:// \ --username REDACT \ --password 'REDACT' \ --branch=master \ --path=. ```...

This is an old issue with Go binaries, various antivirus solutions get confused especially if you embed cryptographic package like Age and OpenPGP which are used in ransomware. I would...

First step would be to encapsulate each command flags into a struct, e.g. https://github.com/fluxcd/flux2/blob/main/cmd/flux/create_image_policy.go#L40 then rewrite the `get` commands to use the https://github.com/fluxcd/flux2/blob/main/cmd/flux/object.go e.g. https://github.com/fluxcd/flux2/blob/main/cmd/flux/get_image_policy.go#L35

@suryapandian can't you change your manifest generator to create a dir with the app name? From: - `development/application1-manifest.yaml` To: - `development/application1/manifest.yaml`

Closing this as we can't replicate the error, please comment here if you still have this issue.

We provide a [script](https://github.com/fluxcd/flux2/blob/main/install/flux.sh) for installing the latest CLI and a [GitHub Action](https://github.com/fluxcd/flux2/tree/main/action), both fetch the latest version using the GitHub releases API. You could use one of two options...

The CRDs are generated with [controller-gen](https://github.com/kubernetes-sigs/controller-tools), we have no control over this process, please submit this issue to Kubernetes or kubeconform.

One workaround would be to use a kustomize remove patch that targets the CRD Kind in all these overlays to delete the `creationTimestamp` field https://github.com/fluxcd/flux2/tree/main/manifests/bases

Flux 0.33 comes with support for Azure auto-login, instead of using a secret and static credentials, Flux is now able to use aad-pod-identity. Docs here: https://fluxcd.io/docs/components/source/helmrepositories/#azure