Closed nrdevau closed 1 month ago
Interesting.. It seems to be related to dev/static/sign
I'll try a static content redeploy, assuming this will leave media as is
bin/magento setup:static-content:deploy -f
did the trick in my situation
Hello @nrdevau
This process should have done nothing to the env.php
to change the deployment config dev/static/sign
information or break the frontend. I'll verify with a test case.
I don't believe I changed that value at the same time, but something in my environment caused things to fall over, my guess is because that was turned on, and maybe others have only tried with it off? Or just not reported it? The test case will verify 😅
@nrdevau https://github.com/genecommerce/module-encryption-key-manager/pull/49
Everything seems fine to me, you can see with FPC disabled the tests have maintained access to version1721980920
so I suspect whatever else went on here, was something on your setup / system not specifically related to key invalidation.
It is hard as theres a lot of moving parts .
Yes, thanks for verifying. Must be something related to either
Hope this serves as a solution for someone else at some point. Who knows!
We generated all our keys on magento cloud and sonassi without issue 🤷
👋 I'm not 100% confident on the cause here, so i'm tweaking the readme.md from your PR and pulling in with other work here
https://github.com/genecommerce/module-encryption-key-manager/pull/55
I haven't seen anyone reference this. Title is the error I'm getting after
Replication Steps
var/report/xx/xxxxxxxxxxxxxxxxxxxxxxx
Stacktrace
Time to go digging