You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when using Archinstall with an user_configuration.json file, the UUID for disk partitions is hardcoded in the obj_id field. Could this UUID rather be generated during the installation process and be unique to each partition?
I think it would be great if Archinstall dynamically assigned the obj_id during the installation process, instead of hardcoding UUIDs in the configuration. This would allow for more adaptable configurations and would be helpful for those who want to automate the installation process across multiple systems without needing to manually update UUIDs every time.
The text was updated successfully, but these errors were encountered:
Technically speaking, the reason why UUID has to be there is if you want to reuse a partition. In all other instances, that field won't be used I believe even if it's there.
To clarify, obj_id is NOT the UUID of the partition. It is a unique internal identifier to correlate the partitions in the user_configuration.json with potential partitions listed in the user_credentials.json under the encryption block.
So there is no hardcoding of any UUIDs, we don't generate our own UUIDs for paritions
describe the request
Currently, when using Archinstall with an user_configuration.json file, the UUID for disk partitions is hardcoded in the
obj_id
field. Could this UUID rather be generated during the installation process and be unique to each partition?I think it would be great if Archinstall dynamically assigned the
obj_id
during the installation process, instead of hardcoding UUIDs in the configuration. This would allow for more adaptable configurations and would be helpful for those who want to automate the installation process across multiple systems without needing to manually update UUIDs every time.The text was updated successfully, but these errors were encountered: