This was always possible, not sure why/how said it was not possible.
this is full option set for configuring interface we have in our testsuite for years now.
so I would think that you would need something like
or something like that depending on your configuration.
But thinking of it now, I am not sure how would this work later when services are bound to this interfaces.
I have tried numerous variations of the <interface> tag, including those you've listed, but none are successful. The server starts, but the services are not listening on multiple interfaces. Specifying <any-ipv4-address/> works of course, but that's not ideal, as I have several interfaces and do not want to expose the services on all of them.
Without <any-ipv4-address/>,<any-ipv6-address/> and <any>, there is a way to set multiple ip which are accessable to the management interface ?
From help from interface menu, those options are looking for a IP for the interface.
For example, NIC
Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether its network interface has a name that matches the given regular expression.
You can start instance with 0.0.0.0 and then you can access with all IPs available on System.