Resoto Worker (
resotoworker) performs all of the collection and cleanup work in Resoto.
A worker is connected to Resoto Core over a websocket connection and simply awaits instructions. By default, it subscribes to the
cleanup actions as well as
Resoto Worker loads collector plugins like AWS, Google Cloud, Slack, Onelogin, etc. Only those plugins have knowledge about how to communicate with each cloud, how to collect resources, and how to clean them up.
There can be one or more workers in a Resoto deployment. A single worker can collect many clouds, or you could have multiple workers each collecting one cloud or account.
Once a worker is started, you do not need to interact with it at all. It will simply wait for work and do its job.
|Unique subscriber ID
|Only log errors
|Resoto Core URI
--override CONFIG_OVERRIDE [<CONFIG_OVERRIDE> ...]
|Override config attribute(s)
|Path to custom CA certificate file
|Path to custom certificate file
|Path to custom certificate key file
|Passphrase for certificate key file
|Turn off certificate verification
CLI options can also be set via environment variables. The environment variable name is the same as the option name, but in uppercase with the prefix
RESOTOWORKER_ and dashes replaced by underscores.
--fork would become
The following are details on how Resoto Worker works internally and how it integrates with Resoto Core.
Upon start up, Resoto Worker discovers and loads all of the available plugins. There are two types of plugins. The first are collector plugins, which are responsible for collecting resources from a cloud. The second are action plugins, which wait for a certain action to occur and are responsible for things like flagging resources for cleanup, tagging or protecting them.
Actions and Tasks
Think of actions and tasks like topics and queues in a messaging system. Actions are broadcast to everyone subscribed for that action. A task is always given to exactly one worker that knows how to handle it.
When the collect workflow within resotocore is triggered (by either an event or a schedule or because the user manually triggered it), resotocore will broadcast a "start collecting all the cloud accounts you know about" message to all the subscribed workers. Once all the workers finish collecting and sent their graph to the core, the workflow will proceed to the next step which would be plan_cleanup. This one tells anyone interested to start planing their cleanup based on the just collected graph data. Once everyone has planed their cleanup and flagged resources that should get cleaned up with the desired.clean = true flag, the workflow proceeds to the cleanup step which again notifies anyone subscribed to now perform cleanup of those flagged resources. Because the cleaner within Resoto Worker has knowledge of all dependencies in the graph, it will ensure that resources are cleaned up in the right order.
When a plugin or a user decides that a resource tag should be added, changed or removed, e.g. by running
> search id = i-039e06bb2539e5484 | tag update owner lukas
Resoto Core will put this tagging task onto a task queue. This task is then consumed by a Resoto Worker that knows how to perform tagging for that particular resource and its particular cloud and account. In our example above where we are setting the tag
owner: lukas for an AWS EC2 instance with ID
i-039e06bb2539e5484 the task would be given to a Resoto Worker that knows how to update AWS EC2 instance tags in that resources account.