Automate Example Rudder
HumDay reads Example Rudder’s own published API description and derives 134 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Example Rudder is
Download OpenAPI specification: [openapi.yml](openapi.yml) # Introduction Rudder exposes a REST API, enabling the user to interact with Rudder without using the webapp, for example in scripts or cronjobs. ## Versioning Each time the API is extended with new features (new functions, new parameters, new responses, ...), it will be assigned a new version number. This will allow you to keep your exist
API host: rudder.example.local
What HumDay can do in Example Rudder
74 documented operations change something in Example Rudder. The 59 most useful are listed here.
- PUTCreate one or several new nodes
/nodes - PUTCreate a new parameter
/parameters - POSTAdd user
/usermanagement - POSTUpdate validated user list
/validatedUsers - DELETERemove an user from validated user list
/validatedUsers/{username} - PUTCreate a rule
/rules - PUTCreate a group
/groups - PUTCreate a secret
/secret/ - PUTCreate a directive
/directives - PUTCreate technique
/techniques - PUTCreate a data source
/datasources - POSTGet a list of CVE details
/cve/list - POSTReload branding file
/branding/reload - PUTCreate a rule category
/rules/categories - PUTCreate a group category
/groups/categories - POSTUpload an inventory for processing
/inventories/upload - POSTUpdate CVE database from file system
/cve/update/fs - DELETEDelete an user
/usermanagement/{username} - POSTTrigger a new policy generation
/system/regenerate/policies - POSTUpdate a secret
/secret/ - POSTUpdate web interface customization
/branding - POSTCreate an archive
/system/archives/{archiveKind} - POSTUpdate user's infos
/usermanagement/update/{username} - POSTTrigger a CVE check
/cve/check - POSTUpdate CVE database from remote source
/cve/update/ - POSTReload both techniques and dynamic groups
/system/reload - POSTReload methods
/methods/reload - POSTImport a ZIP archive of policies into Rudder
/archives/import - POSTTrigger an agent run on all nodes
/nodes/applyPolicy - POSTReload techniques
/techniques/reload - POSTUpdate properties from data sources
/datasources/reload - DELETEDelete a secret
/secret/{name} - DELETEDelete a node
/nodes/{nodeId} - POSTUpdate node settings and properties
/nodes/{nodeId} - DELETEDelete a rule
/rules/{ruleId} - POSTUpdate a rule details
/rules/{ruleId} - DELETEDelete a group
/groups/{groupId} - POSTUpdate group details
/groups/{groupId} - POSTSet the value of a setting
/settings/{settingId} - POSTUpdate cve check config
/cve/check/config - DELETEDelete a directive
/directives/{directiveId} - POSTUpdate a directive details
/directives/{directiveId} - DELETEDelete a parameter
/parameters/{parameterId} - POSTUpdate a parameter's value
/parameters/{parameterId} - POSTReload dynamic groups
/system/reload/groups - DELETEDelete a data source
/datasources/{datasourceId} - POSTUpdate a data source configuration
/datasources/{datasourceId} - POSTTrigger update of policies
/system/update/policies - POSTStop inventory watcher
/inventories/watcher/stop - POSTReload techniques
/system/reload/techniques - POSTStart inventory watcher
/inventories/watcher/start - DELETEDecline a request details
/changeRequests/{changeRequestId} - POSTUpdate a request details
/changeRequests/{changeRequestId} - POSTRestart inventory watcher
/inventories/watcher/restart - POSTTrigger batch for cleaning unreferenced software
/system/maintenance/purgeSoftware - POSTUpdate pending Node status
/nodes/pending/{nodeId} - POSTReload a group
/groups/{groupId}/reload - POSTUpdate properties for one node from all data sources
/nodes/{nodeId}/fetchData - POSTTrigger an agent run
/nodes/{nodeId}/applyPolicy
What HumDay can read from Example Rudder
These are the operations a schedule or a trigger can watch.
- GETList user
/users - GETList all users
/usermanagement/users - GETList all roles
/usermanagement/roles - GETList all endoints
/info - GETList managed nodes
/nodes - GETList all rules
/rules - GETList all groups
/groups - GETList methods
/methods - GETList all secrets
/secret/ - GETReload user
/usermanagement/users/reload - GETList all settings
/settings - GETList all directives
/directives - GETList all global parameters
/parameters - GETList all techniques
/techniques - GETList all data sources
/datasources - GETList pending nodes
/nodes/pending - GETGet a ZIP archive of the requested items and their dependencies
/archives/export - GETList all change requests
/api/changeRequests - GETList versions
/techniques/versions - GETList categories
/techniques/categories - GETGet all CVE details
/cve - GETCheck if Rudder is alive
/status - GETGet branding configuration
/branding - GETGlobal compliance
/compliance - GETList archives
/system/archives/{archiveKind} - GETGet rules tree
/rules/tree - GETList all directives based on a technique
/techniques/{techniqueId}/directives - GETGet groups tree
/groups/tree - GETGet server information
/system/info - GETGet nodes acceptation status
/nodes/status - GETGet server status
/system/status - GETCompliance details for all nodes
/compliance/nodes - GETCompliance details for all rules
/compliance/rules - GETGet information about inventory processing queue
/inventories/info - GETGet healthcheck
/system/healthcheck - GETGet one secret
/secret/{name} - GETGet information about a node
/nodes/{nodeId} - GETGet a rule details
/rules/{ruleId} - GETGet group details
/groups/{groupId} - GETGet information on endpoint in a section
/info/{sectionId} - GETGet last CVE check result
/cve/check/last
How automating Example Rudder works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Example Rudder account.
- Grant access, then go live. You approve the specific Example Rudder operations it may use — and only those.
Automate Example Rudder with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about Example Rudder automation
- Can HumDay connect to Example Rudder?
- Yes. HumDay reads Example Rudder's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 134 operations are documented.
- Do I need to write code to automate Example Rudder?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Example Rudder account.
- What can HumDay do in Example Rudder?
- 74 of the 134 documented operations change something in Example Rudder, and 60 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Example Rudder account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Example Rudder is held behind that approval.
Where this came from
The operations above are read from a published API description for Example Rudder at docs.rudder.io/api/openapi.yml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.