Can HumDay connect to Redhat Patchman engine?

Yes. HumDay reads Redhat Patchman engine's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 21 operations are documented.

Do I need to write code to automate Redhat Patchman engine?

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 Redhat Patchman engine account.

What can HumDay do in Redhat Patchman engine?

3 of the 21 documented operations change something in Redhat Patchman engine, and 18 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Redhat Patchman engine 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 Redhat Patchman engine is held behind that approval.

Automate Redhat Patchman engine

HumDay reads Redhat Patchman engine’s own published API description and derives 21 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 Redhat Patchman engine is

API of the Patch application on [cloud.redhat.com](cloud.redhat.com) Syntax of the `filter[name]` query parameters is described in [Filters documentation](https://github.com/RedHatInsights/patchman-engine/wiki/API-custom-filters)

API host: redhat.local

What HumDay can do in Redhat Patchman engine

3 documented operations change something in Redhat Patchman engine.

DELETEDelete system by inventory id/api/patch/v1/systems/{inventory_id}
POSTView advisory-system pairs for selected systems and advisories/api/patch/v1/views/advisories/systems
POSTView system-advisory pairs for selected systems and advisories/api/patch/v1/views/systems/advisories

What HumDay can read from Redhat Patchman engine

These are the operations a schedule or a trigger can watch.

GETShow me all my systems/api/patch/v1/systems
GETShow me all installed packages across my systems/api/patch/v1/packages/
GETShow me all applicable advisories for all my systems/api/patch/v1/advisories
GETExport systems for my account/api/patch/v1/export/systems
GETShow me all installed packages across my systems/api/patch/v1/export/packages
GETExport applicable advisories for all my systems/api/patch/v1/export/advisories
GETShow me details about a system by given inventory id/api/patch/v1/systems/{inventory_id}
GETShow me metadata of selected package/api/patch/v1/packages/{package_name}
GETShow me details an advisory by given advisory name/api/patch/v1/advisories/{advisory_id}
GETShow me all my systems which have a package installed/api/patch/v1/packages/{package_name}/systems
GETShow me details about a system packages by given inventory id/api/patch/v1/systems/{inventory_id}/packages
GETShow me systems on which the given advisory is applicable/api/patch/v1/advisories/{advisory_id}/systems
GETShow me all package versions installed on some system/api/patch/v1/packages/{package_name}/versions
GETShow me advisories for a system by given inventory id/api/patch/v1/systems/{inventory_id}/advisories
GETShow me all my systems which have a package installed/api/patch/v1/export/packages/{package_name}/systems
GETShow me details about a system packages by given inventory id/api/patch/v1/export/systems/{inventory_id}/packages
GETExport systems for my account/api/patch/v1/export/advisories/{advisory_id}/systems
GETExport applicable advisories for all my systems/api/patch/v1/export/systems/{inventory_id}/advisories

How automating Redhat Patchman engine 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 Redhat Patchman engine account.
Grant access, then go live. You approve the specific Redhat Patchman engine operations it may use — and only those.