Override Service Operation in Microcks .7
A documented Microcks .7 operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Override Service Operation
- PUTChanges data · mock
microcks.local/services/{id}/operation
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Microcks .7 operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Microcks .7 operations
- Create a new TestPOST · changes data
- Create a new SecretPOST · changes data
- Create ImportJobPOST · changes data
- Report and create a new TestCaseResultPOST · changes data
- Upload an artifactPOST · changes data
- Import a snapshotPOST · changes data
- Delete ImportJobDELETE · changes data
- Update ImportJobPOST · changes data
Questions
- Can HumDay override service operation in Microcks .7?
- Yes. This operation is published in Microcks .7's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Microcks .7 data?
- Yes — this is a PUT operation, so it changes something in Microcks .7. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Microcks .7 account.
Where this came from
Read from a published API description for Microcks .7 at raw.githubusercontent.com/microcks/microcks/master/api/microcks-openapi-v1.7.yaml. The description above is the provider’s own wording, not ours. Last published 2023-04-05.