community 
Activate attribute change requests in the Default Sandbox Setup
Currently, if you set an attribute value for a resource in a Blueprint, that attribute value will not be saved to the resource, even if you reserve the resource, until you run the "Activate Topology" CloudShell API/TestShell API Function.
This causes severe inconvenience, because the default setup does not contain a call to this function, and a customer using the system would have no way of knowing why the change in attribute value that he marked in the Blueprint did not take effect.
The solution I propose is to either
- Call the "ActivateTopology" function as part of the Default Setup, during the connectivity phase OR
- Implement a new server API to activate attribute change requests from the Blueprint and call that during the setup script OR
- Implement a new server API to activate attribute change requests from the Blueprint and have it occur automatically upon reserving the Blueprint.
9 People are following this .
