You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we create sha of the zip we could update code by parsing the CodeSha256 and convert it from base641 to hex and then create the key from that. This would be useful for config changes as it would avoid the need for downloading/uploading the code zip file.
The text was updated successfully, but these errors were encountered:
On Mon, Jul 17, 2017 at 12:28 PM, Chris Olszewski ***@***.***> wrote:
If we create sha of the zip we could update code by parsing the CodeSha256
and convert it from base641 to hex and then create the key from that.
This would be useful for config changes as it would avoid the need for
downloading/uploading the code zip file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#284>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABlbivy58k-zO8ViPQq10IUbsyNUz3Gks5sO4qEgaJpZM4OaML2>
.
--
Francis Gulotta
Director of Engineering
Bustle.com / @bustlelabs
If we create sha of the zip we could update code by parsing the
CodeSha256
and convert it frombase641
tohex
and then create the key from that. This would be useful for config changes as it would avoid the need for downloading/uploading the code zip file.The text was updated successfully, but these errors were encountered: