consistency: accept INBUXA_MIGRATE_API_KEY as alias for INBUXA_MIGRATE_TOKEN #21

Closed
opened 2026-10-26 21:34:07 +00:00 by mbunkus · 1 comment

inbuxa-cli uses INBUXA_API_KEY, and the term "API key" is the one used in docs/inbuxa's interface/what you actually have to create. Therefore it'd make sense to have inbuxa-migrate use that term, too, not "token" or "bearer token". For compatibility both the current INBUXA_MIGRATE_TOKEN & the new INBUXA_MIGRATE_API_KEY should be supported, with the latter taking precedence.

`inbuxa-cli` uses `INBUXA_API_KEY`, and the term "API key" is the one used in docs/inbuxa's interface/what you actually have to create. Therefore it'd make sense to have `inbuxa-migrate` use that term, too, not "token" or "bearer token". For compatibility both the current `INBUXA_MIGRATE_TOKEN` & the new `INBUXA_MIGRATE_API_KEY` should be supported, with the latter taking precedence.
Owner

Thanks @mbunkus, done in #22. --auth-bearer now reads INBUXA_MIGRATE_API_KEY first. INBUXA_MIGRATE_TOKEN still works, and if both are set the API key wins. It ships in the next inbuxa-migrate release, and the docs page will switch to the new name then.

Thanks @mbunkus, done in #22. `--auth-bearer` now reads `INBUXA_MIGRATE_API_KEY` first. `INBUXA_MIGRATE_TOKEN` still works, and if both are set the API key wins. It ships in the next inbuxa-migrate release, and the docs page will switch to the new name then.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-migrate#21