Describe the application's registry robot
Report whether a push robot minted on the registry this application publishes to backs its repository login, and when none does, why - the organisation’s project is not provisioned, or the declared registry names no admin_credential_name for Ankra to mint one with. Never contacts the registry. A browser session twin is mounted at the same path without the /api/v1 prefix (cookie authentication).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
Registry credential holding the robot login.
The robot lives on a registry the organisation operates rather than on Ankra's.
Ankra can mint and rotate a robot on this registry: always on the organisation's own registry, and on a declared registry once admin_credential_name names a robot administrator.
Why no robot is provisioned or manageable, and what would change that.
A push robot minted on the registry the application publishes to backs its repository login.
The recorded robot was minted on a registry the application no longer publishes to.