I created a GCE Instance node to handle basic instance operations:
Start
Stop
Reset
Delete
Create
I have also included an example flow that demonstrates a use case of needing to schedule the start/stop of instances. This flow simply lists all instances and then turns an instance on if its off, and off if its on. The node can be explicitly configured via the UI or you can programmatically inject the required value via msg.payload. I've tried to follow the convention
# function node -> gce-instance node
msg.payload = {
projectId: "string",
zone: "string", // e.g. us-central1-a
instance: "string", // instance name when required
operation: "string", // get, list, start, stop, delete, reset
template: "JSON string", // json string template as per API docs
}
After feedback and whether this is something I should continue developing. Happy to implement any changes, conventions, styling, etc. I'd like to keep adding more features/operations and other GCE nodes. Please reach out with any questions!
Hi!
I created a GCE Instance node to handle basic instance operations:
I have also included an example flow that demonstrates a use case of needing to schedule the start/stop of instances. This flow simply lists all instances and then turns an instance on if its off, and off if its on. The node can be explicitly configured via the UI or you can programmatically inject the required value via
msg.payload
. I've tried to follow the conventionAfter feedback and whether this is something I should continue developing. Happy to implement any changes, conventions, styling, etc. I'd like to keep adding more features/operations and other GCE nodes. Please reach out with any questions!
Example flow
Node UI