Possibilty of task config attribute which doesn't cause a reschedule?

So what I’m wondering is whether if say I have a flake_ref and flake_sha attribute, can I specify somehow that, that attribute does not trigger a new allocation? The use case is that even though flake_ref and flake_sha are needed to fetch the flake, drv_sha dictates the actual contents and pins them properly, therefore if flake_ref/sha update it doesn’t necessarily mean that a reallocation is necessary.