v0.7.2

• Currently we have a single config file : the KubeAid Bootstrap Script config file.

  And credentials get picked up, with this precedence order :
  CLI Flag > Environment Variable > KubeAid Bootstrap Script config file.

  A downside of specifying credentials via CLI flags / environment variables is that the credentials will stay in the shell history.

  We need to have a dedicated KubeAid Bootstrap Script secrets file. Any credentials will be specified there.

  We can later have a feature : of automatically backing up the secrets file in an S3 compatible storage, during the cluster bootstrap process.

  Or the user can just save the secrets file in passwordstore / 1password / other password management solutions.

  And the config file will be saved in the KubeAid config's cluster specific directory.

  If the user wants to reinstall / recover a cluster, the user can download the KubeAid Bootstrap Script config and secret files locally, update tokens and credentials (if required) and then use them to run the corresponding command.

• Also, hides this annoying ArgoCD port-forward error :

  E0403 16:48:33.891777   48128 portforward.go:391] "Unhandled Error" err="error copying from remote stream to local
  connection: readfrom tcp4 127.0.0.1:53214->127.0.0.1:53218: write tcp4 127.0.0.1:53214->127.0.0.1:53218: write: broken
  pipe" logger="UnhandledError"
  

• I ran the cluster upgrade aws command. The capi-cluster.values.yaml got weirdly and wrongly formatted : Archisman-Mridha/kubeaid-config@main...Archisman-Mridha:kubeaid-config:kubeaid-kubeaid-demo-aws-1740740791.

  I have to disable yq's formatting.