Adding support for naming a container when using CreateContainer

[jgarverick]

Updated commit that should be based on rebase to current master, then applying just the file changes. I'm not worried about the Nuspec changes as they won't work without altering more things at a csproj level.

[ahmetb]

Thanks!

• Have you tested this manually?

I have just noticed that there's a new parameter called RestartPolicy (#8) and we just use .Config field in there right now. I'm not sure if we have other instances where one property bag type (xxxParameters) contains mixed "query strings" (i.e. name) and "request body parameters" (i.e config).

[jgarverick]

I have. I'm using it in my POC right now and it works like a champ. I can
move it into the config object if you want. I separated it only because it
wasn't listed as part of the config, but given the QueryStringParameter
usage I should be able to make it work.

On Monday, October 6, 2014, Ahmet Alp Balkan [email protected]
wrote:

Thanks! Have you tested this manually?

I have just noticed that there's a new parameter called RestartPolicy (#8
#8) and we just
use .Config field in there right now. I'm not sure if we have another
instances where one object (xxxParameters) contains mixed "query strings"
(i.e. name) and "request body parameters" (i.e config).

—
Reply to this email directly or view it on GitHub
#7 (comment)
.

[jgarverick]

The rest of your requests should be all set. I tested this out locally with my own application and was able to create a named container. I'm assuming we should be all set on this one, and I'll create a separate pull for the other item.