Currently, the driver accepts most of its parameters as name, e.g --cloudstack-template uses the name of the template. This can be a problem since cloudstack does not enforce the name to be an unique field.
It would be interesting if the user could use the id of the field, and not the name, directly. I think this can be done in two ways:
-
add command line args for all fields accepting id directly, eg: --cloudstack-template-id, --cloudstack-zone-id etc.
-
Use the same arguments as now, but check if the provided string matches an id, if not, tries to fetch the id using the provided string as name.
I would be happy to send a PR for this.
What`s your opinion on this, @atsaki?
Currently, the driver accepts most of its parameters as name, e.g
--cloudstack-templateuses the name of the template. This can be a problem since cloudstack does not enforce the name to be an unique field.It would be interesting if the user could use the id of the field, and not the name, directly. I think this can be done in two ways:
add command line args for all fields accepting id directly, eg:
--cloudstack-template-id,--cloudstack-zone-idetc.Use the same arguments as now, but check if the provided string matches an id, if not, tries to fetch the id using the provided string as name.
I would be happy to send a PR for this.
What`s your opinion on this, @atsaki?