For users that execute in CI pipelines it can be a challenge that they want to do one of the following:
create a resilient token that won't suddenly stop working if the person who created it leaves the company
not expose their own token in a pipeline
The ability for certain users (admins likely) to create an additional API token for "robot users" can help save some administration time on the customer side. Currently the workaround that exists today is to create a robot user within the cloud using some distro list email/robot email at the company. This adds additional overhead on the customer side which can be easily solved through a token on the cloud end.
markjmeier
commented
11 months ago
For users that execute in CI pipelines it can be a challenge that they want to do one of the following:
The ability for certain users (admins likely) to create an additional API token for "robot users" can help save some administration time on the customer side. Currently the workaround that exists today is to create a robot user within the cloud using some distro list email/robot email at the company. This adds additional overhead on the customer side which can be easily solved through a token on the cloud end.