Skip to content

chore: provisioner acquirer to respect organization ID of jobs #13874

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

Merged
merged 3 commits into from
Jul 11, 2024

Conversation

Emyrk
Copy link
Member

@Emyrk Emyrk commented Jul 11, 2024

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.

@@ -1829,3 +1829,51 @@ func TestTemplateAccess(t *testing.T) {
}
})
}

func TestMultipleOrganizationTemplates(t *testing.T) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test would always fail prior to this change.

@Emyrk Emyrk requested a review from deansheather July 11, 2024 16:18
@Emyrk Emyrk merged commit 687d953 into main Jul 11, 2024
29 checks passed
@Emyrk Emyrk deleted the stevenmasley/multiple_org_provisioners branch July 11, 2024 16:26
@github-actions github-actions bot locked and limited conversation to collaborators Jul 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants