Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamically assign obj_id in user_configuration.json #3183

Closed
loxoron218 opened this issue Feb 19, 2025 · 2 comments
Closed

Dynamically assign obj_id in user_configuration.json #3183

loxoron218 opened this issue Feb 19, 2025 · 2 comments

Comments

@loxoron218
Copy link

loxoron218 commented Feb 19, 2025

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.

@Torxed
Copy link
Member

Torxed commented Feb 19, 2025

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.

@svartkanin
Copy link
Collaborator

svartkanin commented Feb 19, 2025

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

if not hasattr(self, '_obj_id'):
self._obj_id: uuid.UUID | str = uuid.uuid4()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants