RFC-98 Follow up Forge Dynamic Modules

[BenRomberg]

Thanks for the updated RFC @JuliaDaehne!

If I understand correctly, the new proposal means that we won’t have any APIs to create/update/delete dynamic modules, but just return the currently valid dynamic modules by the dynamicModule function, correct?

@JuliaDaehne

This data will then be cached, ensuring that for any subsequent discovery, the invocation process is not re-executed if the data is already present in the cache.

How long will the dynamicModule function invocation be cached? What happens if we add a new dynamic module to the app’s KVS? How long, until the function will be called again to make the new module available to the users? Or is there some way we can trigger cache invalidation?