Repository navigation
Fixes a regression in 0.2.0. Upgrade if you're on 0.2.0.
Fixed
- 0.2.0 refused to load any profile that set
auth_key_envwithoutauth_key_ssm. Every command failed withprofile '<name>' has auth_key_env but no auth_key_ssm fallback, including configs that followed the README. The two sources are now independent, and both are optional again. auth_key_ssmaccepts any SSM parameter name. In 0.2.0 it took only a fixed set of path prefixes, and the AWS profile and region were derived from the path.
New
auth_key_ssm_profileandauth_key_ssm_region(optional) choose the AWS CLI profile and region for the SSM read. Without them, the read uses your default AWS profile and its configured region. InheritedAWS_*environment variables are still ignored, so an ambient profile or endpoint override can't redirect the read.tailctl bootstraptakes--auth-key-ssm-profileand--auth-key-ssm-region.--auth-key-envand--auth-key-ssmno longer have to be given together.
Upgrading
- Homebrew:
brew upgrade tailctl. - pipx:
pipx upgrade tailctl. - If you set
auth_key_ssmunder 0.2.0, addauth_key_ssm_profileandauth_key_ssm_regionto keep reading with the same AWS profile and region. Config written for 0.1.x loads unchanged.