Which content is stored in the "Dynamic" volume

[Krieke]

Which content is stored in the "Dynamic" volume. We have noticed when we want to start with a complete new "static" configuration that it is best to clean the previously dynamic mounted volume as well. We can of course within our setup choose not to mount the dynamic folder to an external volume, but are thoughts were that this folder might contain certain data which the Portal API might use when the docker was restarted again?

So it would be helpful to know if the dynamic data folder content is of any value within a running Portal API setup.

[DonMartin76]

When creating an initial deployment, it's not important what's in here, and it should be empty.

When operating the API Portal, the dynamic volume is where the user data is kept, i.e. developer applications and subscriptions, including API keys, client ids and secrets and so on. So: This is the volume which has to be kept safe between deployments, otherwise you throw away the end user data.

In case you are just using OAuth 2.0 Client Credentials and API Keys, this is the only persistent data which needs to be kept. The Postgres data can be regenerated if needed.

Only in case you have OAuth 2.0 Implicit Grant Flows or other OAuth 2.0 Flows where you have access tokens and/or refresh tokens issued by Kong, you should try to keep the Postgres database between deployments.

BTW, it will be a lot easier to update container configuration in the future, as you only have to recreate the portal-api container, the rest of the containers will restart themselves, so you will probably not update the entire APIm deployment that often anymore.

[Krieke]

OK clear... the issue can be closed