-
Notifications
You must be signed in to change notification settings - Fork 4
Good day: I'm trying to set CE blueprints but I'm having difficulties doing it. Can you show me the proper syntax for setting it? #14
Comments
What version of the PowerShell module are you using? This was a problem after CloudEndure updated a number of their APIs and the data formats that got returned. This should be fixed in the most recent version, but want to confirm which one you're using @aspersram. |
Name Value PSVersion 5.1.19041.1 |
Looking for the version of the module, something like |
I think I found the issue: I was manually installing the new module but when I ran the set-ceblueprint cmdlet, it was loading the old module. I've uninstalled the old one (as opposed to removing it) and installed the new one. However, if I run the same cmd, here's the err:
|
Also tried setting another property via hashtable: Set-CEBlueprint -InstanceId 35a1773e-3acb-471d-af7c-723facaxe95b -Blueprint @{"runAfterLaunch" = "false"} Update Blueprint
|
ModuleType Version Name ExportedCommands Script 2.0.0 cloudendure {Add-CEUserRoles, Add-CEUserToProject, Get-CEAccount, Get-CEAccountExtendedInfo...} |
ok, i'll need to debug that error from CE, it typically happens when the input doesn't exactly match their expected set of parameters, which aren't documented. On the first issue, it's a parameter set problem, it should be using the default parameter set, so I'll need to make an update to fix it. |
My end goal is to throw the full blueprint at the set-ceblueprint cmdlet. Here's an example of the hashtable I want to apply: Name Value staticIpAction DONT_CREATE |
Good day: I'm trying to set CE blueprints but I'm having difficulties doing it. Can you show me the proper syntax for setting it?
Below is my statement/error:
set-ceblueprint -instanceid 35a1773e-3acb-471d-af7c-723facaxe9b -InstanceType "t2.micro"
Set-CEBlueprint : Cannot retrieve the dynamic parameters for the cmdlet. The cloud environment 6849e59c-29f5-4e10-a459-9d8584c7524b is not supported by this cmdlet yet.
At line:1 char:1
Originally posted by @aspersram in #7 (comment)
The text was updated successfully, but these errors were encountered: