Skip to content

Avoid sending network Ids if not specified#1

Merged
mindjiver merged 1 commit intomindjiver:masterfrom
petrhosek:avoid-sending-networkid-if-not-specified
May 13, 2014
Merged

Avoid sending network Ids if not specified#1
mindjiver merged 1 commit intomindjiver:masterfrom
petrhosek:avoid-sending-networkid-if-not-specified

Conversation

@petrhosek
Copy link
Copy Markdown
Contributor

Specifying network Ids in Basic zone is not allowed. Passing
an empty array of network Ids is not enough as the empty parameter
will still be sent triggering an error. We have to completely avoid
sending the parameter in case the network Ids array is empty.

@mindjiver
Copy link
Copy Markdown
Owner

Hi!

Could you just fix the spelling mistakes in the commit message? :) From a quick glance: s@networki@network@g and s@trigerring@triggering@g

Specifying network Ids in Basic zone is not allowed. Passing
an empty array of network Ids is not enough as the empty parameter
will still be sent triggering an error. We have to completely avoid
sending the parameter in case the network Ids array is empty.
@petrhosek petrhosek changed the title Avoid sending networki Ids if not specified Avoid sending network Ids if not specified May 13, 2014
@petrhosek
Copy link
Copy Markdown
Contributor Author

Done, sorry about that.

mindjiver added a commit that referenced this pull request May 13, 2014
…pecified

Avoid sending network Ids if not specified
@mindjiver mindjiver merged commit 4e9febc into mindjiver:master May 13, 2014
@mindjiver
Copy link
Copy Markdown
Owner

thanks for your contribution @petrhosek ! I should really clean this library up wrt to tests and documentation. Makes me feel a bit bad when I think about the current state :)

Also there is another library which also implements cloudstack support in golang. Perhaps it's time to merge the projects.

@petrhosek
Copy link
Copy Markdown
Contributor Author

I've started testing your CloudStack Packer builder against our local CloudStack deployment and hit various issues, this being one of them. I've already managed to resolve most of the issues and I'll have more pull requests coming to both projects in the following days as I clean up the code a little.

@mindjiver
Copy link
Copy Markdown
Owner

👍

@mindjiver mindjiver mentioned this pull request May 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants