Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Allow re-provisioning of recently de-provisioned resources #825

Merged
merged 2 commits into from
Jun 21, 2024

Conversation

morgsmccauley
Copy link
Collaborator

@morgsmccauley morgsmccauley commented Jun 21, 2024

Provisioning a recently de-provisioned Data Layer would silently fail. This is due to the fact that de/provisioning tasks are stored in-memory, keyed by a hash of the config. So if a provisioning task was recently completed, attempting to re-provision would return that same task.

This PR keys by random UUIDs, instead of hashes, so we can trigger multiple provisioning jobs for a given Indexer/Data Layer, allowing for the Provision > De-provision > Provision flow. To protect against re-provisioning an existing Data Layer, we only start the task after verifying it doesn't already exist. Also removed cache from Provisioner to ensure we are getting accurate results.

@morgsmccauley morgsmccauley requested a review from a team as a code owner June 21, 2024 04:57
@morgsmccauley morgsmccauley merged commit 7303f7a into main Jun 21, 2024
3 checks passed
@morgsmccauley morgsmccauley deleted the fix/re-provisioning branch June 21, 2024 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant