[Enhancement]: Allow the use of Organisation Access Tokens (OATs) for authentication

[phill-lewis]

Description

I couldn't see anything saying this is possible. I know OAT is in Beta so it may not have come through here yet. It would be perfect if we could use an OAT instead of a user PAT to automate our Docker Hub Repository creation/management via this Terraform Provider. I read on the OAT pages that they currently can't be use for REST calls and I imagine that is fundamental to this provider.

Affected Resource(s) and/or Data Source(s)

No response

Potential Terraform Configuration

References

No response

Would you like to implement a fix?

None

[nicks]

Ya, currently OATs only work for image push/pulls. They haven't been plumbed through the REST apis yet

[ryantate-amp]

Given the beta status, would implementing a data source and a resource to list/CRUD OATs also not be feasible at this time? Wondering if the API support is there yet. Otherwise, managing OATs is tied to a manual process.

[etugarinova]

Hi @ryantate-amp! We totally hear you. The API support is not there yet, but we have it planned for Q1.

[sp-aaflalo]

Any news on this ?

I see there are many scope in the OAT available like member management.
So are those available now ?

[martin-traverse]

Hi - we would also like this. Even to assign permissions for existing teams, PAT won't work because it can't read the team data source.

[dirsigler]

Is there anything the community can support with ? I have to be honest that it's kinda weird that this gets implemented on the backend side without any REST API available.

If the API is there we might can just provide the feature addition to the provider ourselves - if the API documentation is updated.

[vagharsh]

the REST API is available at https://docs.docker.com/reference/api/hub/latest/#tag/org-access-tokens/paths/~1v2~1orgs~1%7Bname%7D~1access-tokens/post