seroron

Thank you for your review. I tested the following pattern. ``` attributes: name: "newvm" empty_string: int_type: 123 VMGROUP: | [ ROLE = "node", VMGROUP_ID = "14" ] ```

I will stop making changes to attributes parameter. I want Vector Attributes. https://docs.opennebula.io/6.4/management_and_operations/references/template.html#syntax So, I will add vector_attributes parameter. ``` vector_attributes: GRAPHICS: | [ LISTEN = "0.0.0.0", TYPE = "VNC"...

Or it could be this way. ``` vector_attributes: GRAPHICS: LISTEN: "0.0.0.0" TYPE: "VNC" VMGROUP: ROLE: "node" VMGROUP_ID: "14" ``` I need to consider whether the list is nested. I will...

@russoz Thank you for your comment. If ``` attributes: vmgroup: ROLE: node" VMGROUP_ID: 14 ``` it will be sent to OpenNebula as ``` VMGROUP="{'ROLE': 'node', 'VMGROUP_ID': 14}" ``` This is...

I'm sorry, I have misunderstood about @russoz's question, so I wrote something different. I was considering about YAML syntax at https://github.com/ansible-collections/community.general/pull/5045#issuecomment-1206489527. As written by @nilsding, I also think that duplicate...

As a result of the experiment, it was found that even if I send duplicate keys in vector attributes, only the first one is registered in the user template field...

Sorry for the late reply. Since the label has a separate paramater, it do not usually be set in attributes. However, there is a possibility that free text will be...