You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This can be a problem since cloudstack does not enforce the name to be an unique field.
You're right. This can be a problem when there are duplicate names.
I think 1 is better because it is clear that the argument is id and other drivers like openstack do so too.
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?
The text was updated successfully, but these errors were encountered: