Skip to content

Conversation

@ivantodorovich
Copy link
Member

click-odoo-contrib is not installed in our images, so we end up removing click-odoo-update from marabunta file every time we do a release.

Moreoever, I doubt marabunta is the right place for it.
IMHO I would reduce our dependency on marabunta, so I would rather execute elsewhere, like in the image start-entrypoint.

@simahawk are you already using it in one of your projects? I will start experimenting with ssv

@simahawk
Copy link
Member

simahawk commented Dec 3, 2025

AFAIR it was done this way to make it explicit and to leave a bit of control on what runs.
Do you have a proposal for the other implementation?
Also, keep in mind that we need a script to run on existing projects to compute the original hash.
Please check this 1st draft by Guewen from a long time ago https://github.com/camptocamp/cosanum_odoo/pull/647

@ivantodorovich
Copy link
Member Author

I'm playing a little bit here: https://github.com/camptocamp/ssv_odoo/commit/24273edc9f850a4a51552b8aab1d16a2e05c10b9

In this case it's a new project, not yet live, so we don't really care about seeding the checksums.
For existing projects, I would perhaps seed the checksums in a song on the same release where click-odoo-update is integrated. The song (marabunta) is executed before the start-entrypoint, so it'd work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants