Deployment Data Background Refetching#747
Open
jjoderis wants to merge 16 commits into
Open
Conversation
…on from the engines and updates the db if a deployment has been removed from the engine it is expected to be on
…ble when the user requests the removal
…he database instead of having to fetch it from the reachable engine This should speed up loading the data since we don't have to aggregate the data over all available engines. It is now also possible to see deployed processes where the engine is currently not available and to filter out deployments the user should not be able to see.
…d of fetching it from the available engines
…ts instances from the database instead of fetching it from the available engines
PROCEED_PUBLIC_DEPLOYMENT_REFETCHING_INTERVAL controls how frequently thhe interval run If PROCEED_PUBLIC_PROCESS_AUTOMATION_ACTIVE is set to false the loop is disabled
…er for its conclusion or for the conclusion of the last fetch in the refetch timeout
…atabase with optional fetching if the data has not been fetched inside the configured timeout
…se with optional refetching if the data is older than the configured refetch timeout
…the database with optional refetching if the data is older than the configured refetch timeout
…ployment list will count instances and versions of deployments that have been deleted
…t-data-background-refetching
…t-data-background-refetching
This comment has been minimized.
This comment has been minimized.
|
✅ Successfully created Preview Deployment. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Instead of always fetching the latest deployment information from all available machines every time a user tries to access it deployment and instance data is now served from the database. To ensure that the user has access to up to date information this PR adds a refetch loop, that runs as long as a user is connected to the MS, which fetches the latest information for all deployments known to the MS from all available engines and updates the deployment and instance data in the database.
Details