Operator token post upgrade

I’ve just practiced upgrading from influxdb 1.8 to 2.7 on a rocky linux vm.

I wanted to create new users for which I’d need the operator token, which was not previously listed, so I executed influx auth create --org --operator to generate a token, which it did.

The documentation at Create an API token in InfluxDB | InfluxDB OSS v2 Documentation says:

To view or create an operator token with the InfluxDB UI, api/v2 API, or influx CLI after the setup process is completed, you must use an existing operator token.

I was able to execute the command a 2nd time, and again got a token. How does influxdb determine that the setup process is completed so it does not generate a new token without me supplying a token? Is the documentation outdated, or is my understanding wrong?

To answer my own question: it looks like influxdb puts the operator token into ~/.influxdbv2/configs upon creation that’s why it appears to be working for me.

Can anyone please confirm?

Hello @buzzlightyear,
yes it creates one upon creation. You’re correctly

1 Like