Releasing a New Microservice
When releasing a new microservice you'll need to configure some things to get it online, depending on what your microservice does. Most of the configurations has to be done for both production and acceptance.
Deployment
Client ID and Secret
A Client-ID and secret can be created using True-CLI using the following command:
true-cli clients:create --environment=production --organization_id=NLTRU --name=[microservice]
Repeat for acceptance:
true-cli clients:create --environment=acceptance --organization_id=NLTRU --name=[microservice]
Or using the accounts frontend on production and acceptance (not recommended).
Scope
Scopes can be created in accounts using it's frontend.
Scopes have to be made private when only used for microservice to microservice communication. If that's the case the clients of the corresponding microservices should get this as pre authorized scope.
This is also a good moment to add scopes to the Client you just created.
Roles
Creating roles has no ui at this moment and should be created directly in the accounts database ðŸ˜.
Database
Ask Infra to create a database, user and password on the kubernetes database cluster.