coder tokens create
lifetime parameter is confusing
#14750
Labels
bug risk
Prone to bugs
customer-reported
Bugs reported by enterprise customers. Only humans may set this.
First of all, when creating automation tokens (e.g. for coder/setup-action), you typically want either an unlimited lifetime or a lifetime specified in years/months not hours (which is the largest unit supported by our tokens create command).
This leads to instructions like:
coder token create --lifetime 8760h --name "GitHub Actions"
and mental arithmetic to figure out that token exists for a year.
Secondly, our default lifetime in the CLI appears quite arbitrary at 30 days. A more reasonable default is unlimited, and if the deployment doesn't allow that we can retry the request with whatever the maximum lifetime is.
The text was updated successfully, but these errors were encountered: