What
Since PR #527 we have a portable hashing function to get the hash of the run-targets. Currently we assume that no hash collisions happen which is a bit unsafe. But with the changes we could validate that no hash collisions happen in the python script that is ran to validate configs lifecycle_config.py by implementing the same hashing function in python.
I think for now it shall just exit and communicate the error, I don't think we should append or modify the name since we might get into weird behaviour.
Acceptance Criteria (DoD)
- Script validates names and exits 1 if a hash collision is detected.
How
No response
What
Since PR #527 we have a portable hashing function to get the hash of the run-targets. Currently we assume that no hash collisions happen which is a bit unsafe. But with the changes we could validate that no hash collisions happen in the python script that is ran to validate configs lifecycle_config.py by implementing the same hashing function in python.
I think for now it shall just exit and communicate the error, I don't think we should append or modify the name since we might get into weird behaviour.
Acceptance Criteria (DoD)
How
No response