Invalidate cache on change of apikey / enterprise trail #282
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #260
When caching is active, the first request would be cached and if the apikey / enterprise trail is started afterward, it would lead to not being able to install enterprise trail apps
Note:
There is still an open scenario, that when the user changes config.php manually to update licensekey and apikey that the cache would persist.
We should document that changing/adding theses values requires a cache invalidation