We currently cheat on generating unique deployment hashes by reusing the commit hash, the problem is you can technically have multiple deployments of a single commit if you have GitHub Actions redo the action/deploy or eventually when you click the "redeploy" button on the UI. We should have an attempt number associated so that we don't blow away the logs of a previous attempt of the same commit being deployed (in my usage, I do this frequently, mainly while developing and a deploy fails).
Justintime50
commented
1 year ago
We currently cheat on generating unique deployment hashes by reusing the commit hash, the problem is you can technically have multiple deployments of a single commit if you have GitHub Actions redo the action/deploy or eventually when you click the "redeploy" button on the UI. We should have an attempt number associated so that we don't blow away the logs of a previous attempt of the same commit being deployed (in my usage, I do this frequently, mainly while developing and a deploy fails).