By default in GNS3 builtin nodes are always on. Meaning that you cannot start/stop the when they are added to your topology.
The problem is that the ansible module gns3_project marks as changed when trying to shutdown these nodes. The idea would be to skip these nodes from the check so the action ba fully idempotent.
For this I need some kind of builtin attribute set on the Node object in gns3fy
By default in GNS3 builtin nodes are always on. Meaning that you cannot start/stop the when they are added to your topology.
The problem is that the ansible module
gns3_projectmarks aschangedwhen trying to shutdown these nodes. The idea would be to skip these nodes from the check so the action ba fully idempotent.For this I need some kind of
builtinattribute set on theNodeobject in gns3fy