Can HumDay connect to Microcks .7?

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

Do I need to write code to automate Microcks .7?

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 Microcks .7 account.

What can HumDay do in Microcks .7?

16 of the 44 documented operations change something in Microcks .7, and 28 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Microcks .7

HumDay reads Microcks .7’s own published API description and derives 44 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 Microcks .7 is

API offered by Microcks, the Kuebrnetes native tools for API and microservices mocking and testing (microcks.io)

API host: microcks.local

What HumDay can do in Microcks .7

16 documented operations change something in Microcks .7.

POSTCreate a new Test/tests
POSTCreate a new Secret/secrets
POSTCreate ImportJob/jobs
POSTReport and create a new TestCaseResult/tests/{id}/testCaseResult
POSTUpload an artifact/artifact/upload
POSTImport a snapshot/import
DELETEDelete ImportJob/jobs/{id}
POSTUpdate ImportJob/jobs/{id}
DELETEDelete Secret/secrets/{id}
PUTUpdate Secret/secrets/{id}
DELETEDelete Service/services/{id}
PUTStop an ImportJob/jobs/{id}/stop
PUTStart an ImportJob/jobs/{id}/start
PUTActivate an ImportJob/jobs/{id}/activate
PUTUpdate Service Metadata/services/{id}/metadata
PUTOverride Service Operation/services/{id}/operation

What HumDay can read from Microcks .7

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

GETSearch for Services and APIs/services/search
GETGet ImportJobs/jobs
GETExport a snapshot/export
GETGet Secrets/secrets
GETGet Services and APIs/services
GETGet the ImportJobs counter/jobs/count
GETGet the Secrets counter/secrets/count
GETGet the Services counter/services/count
GETGet features configuration/features/config
GETGet authentification configuration/keycloak/config
GETGet the already used labels for Services/services/labels
GETGet ImportJob/jobs/{id}
GETGet TestResult/tests/{id}
GETGet Secret/secrets/{id}
GETGet Service/services/{id}
GETGet Resource/resources/{name}
GETGet latest tests results/metrics/tests/latest
GETGet events for TestCase/tests/{id}/events/{testCaseId}
GETGet messages for TestCase/tests/{id}/messages/{testCaseId}
GETGet top invocation statistics for a day/metrics/invocations/top
GETGet aggregated invocation statistics for a day/metrics/invocations/global
GETGet aggregation of conformance metrics/metrics/conformance/aggregate
GETGet TestResults by Service/tests/service/{serviceId}
GETGet Resources by Service/resources/service/{serviceId}
GETGet aggregated invocations statistics for latest days/metrics/invocations/global/latest
GETGet the TestResults for Service counter/tests/service/{serviceId}/count
GETGet conformance metrics for a Service/metrics/conformance/service/{serviceId}
GETGet invocation statistics for Service/metrics/invocations/{serviceName}/{serviceVersion}

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