Automate ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management
HumDay reads ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management’s own published API description and derives 16 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.
Automate ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management
What ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management is
ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management described using OpenAPI.
API host: etsi.local
What HumDay can do in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management
8 documented operations change something in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management.
- POSTRegisters a notification endpoint to notify application package operations
/user_defined_notification - POSTCreate a resource for on-boarding an application package to a MEO
/app_packages - DELETEDeletes the individual subscription to notifications about application package changes in MEO.
/subscriptions/{subscriptionId} - POSTSubscribe to notifications about on-boarding an application package
/subscriptions - DELETEDeletes an individual application package resources
/app_packages/{appPkgId} - PATCHUpdates the operational state of an individual application package resource
/app_packages/{appPkgId} - PUTUploads the content of application package.
/app_packages/{appPkgId}/package_content - PUTUploads the content of application package.
/onboarded_app_packages/{appDId}/package_content
What HumDay can read from ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management
These are the operations a schedule or a trigger can watch.
- GETUsed to represent an individual subscription to notifications about application package changes.
/subscriptions/{subscriptionId} - GETQueries information relating to on-boarded application packages in the MEO
/app_packages - GETused to retrieve the information of subscriptions to individual application package resource in MEO
/subscriptions - GETQueries the information related to individual application package resources
/app_packages/{appPkgId} - GETReads the content of the AppD of on-boarded individual application package resources.
/app_packages/{appPkgId}/appd - GETReads the content of the AppD of on-boarded individual application package resources.
/onboarded_app_packages/{appDId}/appd - GETFetch the onboarded application package content identified by appPkgId or appDId.
/app_packages/{appPkgId}/package_content - GETFetch the onboarded application package content identified by appPkgId or appDId.
/onboarded_app_packages/{appDId}/package_content
How automating ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management 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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management account.
- Grant access, then go live. You approve the specific ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management operations it may use — and only those.
Automate ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management with these
- Zoom369 operations
- Telnyx361 operations
- Twilio199 operations
- Twilio Preview147 operations
- CallFire Documentation122 operations
- Twilio Conversations101 operations
- Twilio Taskrouter60 operations
- Twilio Verify53 operations
- Twilio Autopilot52 operations
- Twilio Flex50 operations
- Twilio Sync48 operations
- Twilio Trusthub48 operations
Categories
Questions about ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management automation
- Can HumDay connect to ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management?
- Yes. HumDay reads ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 16 operations are documented.
- Do I need to write code to automate ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management?
- 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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management account.
- What can HumDay do in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management?
- 8 of the 16 documented operations change something in ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management 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 ETSI GS MEC 010 2 Part 2 Application lifecycle, rules and requirements management is held behind that approval.
Where this came from
The operations above are 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. Descriptions are the provider’s own words, not ours. Last published 2021-07-20.