Surely you'd still need to know what you're deploying on. Can't plop an x86_64 JVM on an ARM host or vice versa, at least if you want them to run.
It's possible if you have enough abstraction layers. At my company there are a few systems with Java runtime flags specified in the service source code, but deployment configuration in a separate infrastructure-as-code repository. Switching between CPU architectures is normally transparent if you don't rely on native code libraries.
That’s what docker base images are for so don’t count on these two concerns being colocated.
If it’s Java, Node, etc the binary dependencies are platform specific and 100% if your code is not unless you try very hard.
That's where you're wrong buddy /s
https://github.com/elide-dev/madura
Just a compiler, but a runner isn't impossible.
I think the idea is that you’re already running the appropriate JVM on each architecture, but want to push a global command line flag update to every JVM you run, regardless of architecture, that prevents this exploit.
Until, presumably, there’s fixes and you can test, update etc.