triggerdotdev
feat: Allow segmenting tasks into multiple deploy
Is your feature request related to a problem? Please describe.
I have 10-12 tasks, some uses headless Playwright, some uses Headed mode and some are not even using playwright at all. Some may need custom build extension and some need bulk load of aptGet and additionalPackages.
I would like to keep the image separate instead of building it all in same single deployment image.
Describe the solution you'd like to see
Like to see a way to host multiple Tasks in same Project deployed separately. A bundle config which will bundle related tasks into one image or other during deploy and still keep all my tasks.
Describe alternate solutions
Possible option could be a special extension/config to identify group of tasks to bundle together. one way to do is to export bundle name or config from tasks like export bundleName = 'bundle1.
Additional information
No response
@gautamsi do you want this because of the start times?
There are trade offs with multiple images, especially with warm starts, where it can be slower to have more inages
it is not the start time, I like to keep my images clean and free of unwanted dependencies. I also noticed that one of my headless one gives some error when extension headless value is set to false.