chore: provisioner acquirer to respect organization ID of jobs #13874
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.
The domain check to choose what provisioned to give clearance to is defined by the
contains
function. This omitted the organization ID check, so the wrong provisioner could be given clearance, and the job would not be grabbed.When organization ID was added to the jobs, it was only added to the
domainKey
function. This now includes it in both places.A 30s update interval would eventually make it work.
What this does
The pubsub message when a job is posted now chooses the right provisionerd to awaken when multiple organizations exist.