Deterministic hash#731
Conversation
|
same hashes for me for the 3 deployment methods :) |
|
We need to add the deployment variables in this hash too. 2 solutions:
|
|
This pull request has been mentioned on MESG Community. There might be relevant details there: https://forum.mesg.com/t/services-hash-are-different-from-downloaded-tarball-and-remote-git/211/6 |
…sh-with-env Add env in hash calculation
|
This pull request has been mentioned on MESG Community. There might be relevant details there: https://forum.mesg.com/t/services-hash-are-different-from-downloaded-tarball-and-remote-git/211/7 |
de2d453 to
52af70e
Compare
|
Did some fixes here #804 @mesg-foundation/core can you have a look |
…sh-fix Deterministic hash - refactor and fix deployment
|
I cannot with GitHub because i am the creator on the PR but I still approve :) |
Co-Authored-By: krhubert <krhubert@gmail.com>
ilgooz
left a comment
There was a problem hiding this comment.
code lgtm, manual tests are ok
|
Oh yeah 🍾 🍾 🍾 🍾 |
|
This pull request has been mentioned on MESG Community. There might be relevant details there: https://forum.mesg.com/t/services-hash-are-different-from-downloaded-tarball-and-remote-git/211/12 |
Implementation of https://forum.mesg.com/t/services-hash-are-different-from-downloaded-tarball-and-remote-git/211/5
Docker hash are not deterministic.
This PR use the archive to create the service hash.
It very simple are works well:
From github archive
From local git
From remote git
Please try the remote ones on your computer and tell me if you have the same or different hash!