Layer UUID hook

[mattiagiupponi]

The current generation of the UUID for the Layers is based on those two lines:

instance.uuid = str(uuid.uuid1()) in geonode/geonode/layers/models.py
layer_uuid = str(uuid.uuid1()) in geonode/geonode/upload/upload.py

We want to let the UUID creation be pluggable and let the user use his own UUID generator based on their needs.

if hasattr(settings, 'LAYER_UUID_HANDLER') and settings.LAYER_UUID_HANDLER != '':
        from geonode.layers.utils import get_uuid_handler
        instance.uuid = get_uuid_handler()(instance).create_uuid()

And is enough to add this config in settings.py by specifying the object that is responsible to manage the new UUID

LAYER_UUID_HANDLER = "mymodule.myfile.MyObject"

More information related to the configuration are available in this PR

Documentation PR at this link

[gannebamm]

Will this interfere with #6711?

[mattiagiupponi]

Hey, @gannebamm thanks for the comment.
As you can see in this part of the code (pr)

geonode/geonode/layers/models.py

Lines 620 to 626 in ce20d4d

	if hasattr(settings, 'LAYER_UUID_HANDLER') and settings.LAYER_UUID_HANDLER != '':
	logger.debug("using custom uuid handler In pre_save_layer")
	from geonode.layers.utils import get_uuid_handler
	instance.uuid = get_uuid_handler()(instance).create_uuid()
	else:
	if instance.uuid == '':
	instance.uuid = str(uuid.uuid1())

The UUID will change only if a new handler is defined, otherwise will continue using the old version of the UUID
As far as I can see, the #6711 should not impact your development, but I don't have enough context on it, because from the code of the utils.py looks like that the UUID is read from the XML file and not defined on run-time.
So, if you decide to override the way to save the UUID (since is a Charfield could be anything) if you upload the metadata you (user) should have enough context of what's going on.
This is just an observation, maybe @afabiani could help us more :)