in vRA 7.X control center logging tab used to provide to increase the global worklfow tokens settings for last # of executuons/workflow tokens. It seems that is missing in vRA 8.6.X. Any idea how to increase this to a different number?
I think it is there as always.
- Go to Advanced Options in vRO Control Center
- Change the value of Maximum number of preserved runs per workflow to your needs. (I set it to 10)
- Click Save and wait for server to restart.
If that doesn't work by any chance. Then, you can try this other method.
- Go to System Properties in vRO Control Center
- Add a new property ch.dunes.task.max-workflow-tokens with value of your choice
- Click Add and Click Save changes and wait for server to restart.
I think it is there as always.
- Go to Advanced Options in vRO Control Center
- Change the value of Maximum number of preserved runs per workflow to your needs. (I set it to 10)
- Click Save and wait for server to restart.
If that doesn't work by any chance. Then, you can try this other method.
- Go to System Properties in vRO Control Center
- Add a new property ch.dunes.task.max-workflow-tokens with value of your choice
- Click Add and Click Save changes and wait for server to restart.
Thanks that helped.
Do you know if an API call exists for these settings to change?
Yes. We can use properties-controller in the vco-controlcenter API for this purpose. Remember to use root creds to login.
POST /properties
body =
{ "error": "string", "id": "string", "properties": [ { "key": "ch.dunes.task.max-workflow-tokens", "value": "10", "description": "Max WF Tokens" } ] }
OR curl:
curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{ \ "error": "string", \ "id": "string", \ "properties": [ \ { \ "key": "ch.dunes.task.max-workflow-tokens", \ "value": "10", \ "description": "Max WF Tokens" \ } \ ] \ }' 'https://vro_fqdn.domain.local/vco-controlcenter/api/properties'
Important: In case, there are already existing properties added in your vRO, follow the below steps. Otherwise, above step would be enough.
Just do a GET on /properties and save its output. That output has already existing properties on your vRO. We have to pass them as well in the POST body.
{ "error": null, "id": "null", "properties": [ { "key": "o11n.plugin.SQL.classpath", "value": "/var/run/vco/plugins/SQL/lib/mysql-connector-java-8.0.12.jar", "description": "SQL connector" }, { "key": "com.vmware.js.allow-local-process", "value": "true", "description": "allow to execute local processes" }, { "key": "com.vmware.o11n.sso.basic-authentication.enabled", "value": "true", "description": "Basic Authentication for web service" }, { "key": "com.vmware.vro.extensions.profiler.enabled", "value": "true", "description": null }, { "key": "ch.dunes.task.max-workflow-tokens", "value": "10", "description": "Max WF Tokens" } ] }
This way you will preserve the existing properties.
Please mark as correct if it works for you. That would be great.
Thanks that helps a lot too