Updates the operational state of an individual application package in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management
A documented ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management 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
Updates the operational state of an individual application package resource
- PATCHChanges data · app-pkgm
etsi.local/app_packages/{appPkgId}
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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management 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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management operations
- Registers a notification endpointPOST · changes data
- Create a resource for on-boarding an application package to a MEOPOST · changes data
- Deletes the individual subscriptionDELETE · changes data
- Subscribe to notifications about on-boarding an application packagePOST · changes data
- Deletes an individual application package resourcesDELETE · changes data
- Uploads the content of application packagePUT · changes data
- Uploads the content of application packagePUT · changes data
- Used to represent an individual subscriptionGET · reads data
All 16 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management operations
Questions
- Can HumDay updates the operational state of an individual application package in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management?
- Yes. This operation is published in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management'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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management data?
- Yes — this is a PATCH operation, so it changes something in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management. 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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management account.
Where this came from
Read from a published API description for ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management at forge.etsi.org/rep/mec/gs010-2-app-pkg-lcm-api/raw/v2.1.1/MEC010-2_AppPkgMgmt.yaml. The description above is the provider’s own wording, not ours. Last published 2021-07-20.