We have a docker container that we include in all our CI/CD workflows that publishes generates and publishes documentation to Confluence.
At present this works by having two GitHub organisation secrets containing
The problem I am trying to solve is that we don't want the user to be locked to an individual with their expiring PAT token. In effect we want a service account to use with our CI/CD process.
Is there an official way of doing this?
Is it simply a case of creating a CICD user just as for any other account with an associated PAT token?
There is no "official" way to do this except to build a Confluence cloud addon with an api which is exposed to your container. This is a lot of work and maintenance.
The pragmatic way is to use a service account user, give this account minimal rights, and create an API token for this account. This allows you to access the Confluence cloud API with BasicAuth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.