How is id main in <create_config>?

When I use gvm-cli and openvas-cli , I find there has a uuid in <create_config>:
<config id=“daba56c8-73ec-11df-a475-002264764cea”>

But when this config has been created ,it’s id isn’t daba56c8-73ec-11df-a475-002264764cea , so I run the xml without id:
I find it works , so I can’t understand how is id main in <create_config>?

Sorry I don’t understand your question.

A <create_config/> returns a <create_config_response/> response with the uuid of the created scan config as the id attribute as depicted here

This uuid can be used to request the details of the config with <get_configs id="$uuid"/>


there has two id , I can’t find the first id in tasks.db,the second id is important because I need use it to create a task
I guess maybe the first config id is surplus

Ok now I understand. Create config is a bit special compared to the other create commands. You have to create either a copy of an existing scan config via passing a <copy>$UUID</copy> to your request or pass all settings via a <get_configs_response> element. Both requests will always create a NEW scan config which a NEW uuid chosen by gvmd. The uuid of the created config is returned in the <create_config_response/>

Please take a look at carefully!