-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Factor out method to get resolved TaskDefinition #3378
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
🟢 CI successful 🟢Thanks |
// defined in the Graph. Later, this will get Pipelines defined in the task's workspace as well. | ||
func (g *CompleteGraph) getResolvedTaskDefinition(taskID string, taskName string) (*fs.TaskDefinition, error) { | ||
return getTaskFromPipeline(g.Pipeline, taskID, taskName) | ||
} |
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.
This is where we'll implement the magic in #2706
The way we resolve a taskDefinition will change once we start allowing workspaces to create their own config so it makes sense to factor this method out first.
f6b0c1c
to
f15a498
Compare
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'm not convinced we won't want to pre-resolve everything before getting here, but this doesn't materially change anything and seems fine.
Let's chat about that, considering the other conversation we had today about pre-calculated task hashes as well. Want to make sure I'm not overlooking anything. |
The way we resolve a taskDefinition will change
once we start allowing workspaces to create their own config so it makes sense to factor this method out first.