-
Notifications
You must be signed in to change notification settings - Fork 887
chore: Separate the provisionerd server into it's own package #4940
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
Conversation
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
This code should be thoroughly tested now that we understand the abstraction. I separated it to make our lives a bit easier for external provisioner daemons as well!
dd9dc1d
to
dfa73b3
Compare
coadler
approved these changes
Nov 8, 2022
Comment on lines
+914
to
+932
// WorkspaceProvisionJob is the payload for the "workspace_provision" job type. | ||
type WorkspaceProvisionJob struct { | ||
WorkspaceBuildID uuid.UUID `json:"workspace_build_id"` | ||
DryRun bool `json:"dry_run"` | ||
} | ||
|
||
// TemplateVersionDryRunJob is the payload for the "template_version_dry_run" job type. | ||
type TemplateVersionDryRunJob struct { | ||
TemplateVersionID uuid.UUID `json:"template_version_id"` | ||
WorkspaceName string `json:"workspace_name"` | ||
ParameterValues []database.ParameterValue `json:"parameter_values"` | ||
} | ||
|
||
// ProvisionerJobLogsNotifyMessage is the payload published on | ||
// the provisioner job logs notify channel. | ||
type ProvisionerJobLogsNotifyMessage struct { | ||
CreatedAfter int64 `json:"created_after"` | ||
EndOfLogs bool `json:"end_of_logs,omitempty"` | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
random nit; it feels weird that these are at the bottom
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i had them at the top and it felt weird too... tbh they are weird structs
96f963c
to
a57a934
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This code should be thoroughly tested now that we understand the abstraction.
I separated it to make our lives a bit easier for external provisioner daemons as well!