-
Notifications
You must be signed in to change notification settings - Fork 456
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
chore: fleet improvements #3438
Conversation
TBonnin
commented
Feb 3, 2025
•
edited
Loading
edited
- adding 'image' column to deployment
- it will make it easy to switch to another image without having to change fleet code (for example if we move runner to the unified image).
- Note: the column is not used by fleet supervisor yet. Coming in next PR :)
- checking if the image exist when rolling out to avoid rolling out while master is building
- add 'notes' column to node_overrides
- won't be used by the app but I wanted a text column where we can manually enter useful information like the name of the customer or 'Thomas's runner'
- making image, cpu_mill, memory_mb, storage_mb columns nullable in the node_overrides table. I will change the logic: if value is null, fleet will pick default values instead of having to insert specific values when overriding, especially useful for the image that changes with each deployment
6daceb9
to
93e2df3
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.
🙌🏻
} | ||
return Ok(DBDeployment.to(inserted)); | ||
}); | ||
} catch (err) { | ||
return Err(new FleetError(`deployment_creation_failed`, { cause: err, context: { commitId } })); | ||
console.log(err); |
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.
Not sure if this was intended or a leftover
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.
🤦
previousDeployment = (await deployments.create(dbClient.db, generateCommitHash().unwrap())).unwrap(); | ||
activeDeployment = (await deployments.create(dbClient.db, generateCommitHash().unwrap())).unwrap(); | ||
previousDeployment = (await deployments.create(dbClient.db, generateImage().unwrap())).unwrap(); | ||
activeDeployment = (await deployments.create(dbClient.db, generateImage().unwrap())).unwrap(); |
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.
.unwrap().unwrap().unwrap().unwrap()
😆
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.
93e2df3
to
938c81d
Compare
- adding 'image' column to deployment - it will make it easy to switch to another image without having to change fleet code (for example if we move runner to the unified image). - Note: the column is not used by fleet supervisor yet. Coming in next PR :) - checking if the image exist when rolling out to avoid rolling out while master is building - add 'notes' column to node_overrides - won't be used by the app but I wanted a text column where we can manually enter useful information like the name of the customer or 'Thomas's runner' - making image, cpu_mill, memory_mb, storage_mb columns nullable in the node_overrides table. - I will change the overiding logic: if value is null, fleet will pick default values instead of having to insert specific values when overriding, especially useful for the image that changes with each deployment
938c81d
to
bd66039
Compare