Prior to APIM version 4.4.10 and the fix for this issue, when configuring dynamic properties for an API, values would be fetched immediately once the change was deployed for the first time, and then as per the cron schedule. Now, values are no longer fetched initially and only at the first iteration of the cron schedule.
To Reproduce
Steps to reproduce the behaviour:
Configure dynamic properties on an API (I've seen this behaviour on new and existing APIs created by the wizard and using CRDs/GKO), using a URL that returns a response and a valid JOLT expression. I used this cron schedule: 0 */30 * * * *.
Deploy the API to start the dynamic properties service.
Expected behaviour
Values are fetched immediately and are visible on the properties page in the APIM console.
Current behaviour
Values are only fetched at the first iteration of the cron expression.
mamayadi
commented
1 month ago
Describe the bug
Prior to APIM version 4.4.10 and the fix for this issue, when configuring dynamic properties for an API, values would be fetched immediately once the change was deployed for the first time, and then as per the cron schedule. Now, values are no longer fetched initially and only at the first iteration of the cron schedule.
To Reproduce
Steps to reproduce the behaviour:
0 */30 * * * *.Expected behaviour
Values are fetched immediately and are visible on the properties page in the APIM console.
Current behaviour
Values are only fetched at the first iteration of the cron expression.
Environment
Gravitee APIM v4.4.10