FailedConsole Output

Started by GitLab push by Elian Kraja
Obtained Jenkinsfile.mec from git git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on build3.forge.etsi.org in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-011-pipeline
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/stf606-draft, since it originates from another repository
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1b7fd86ec22366ba540a1592a8fd8d054bae57ce (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1b7fd86ec22366ba540a1592a8fd8d054bae57ce
Commit message: "added openapi-cli image version"
 > git rev-list --no-walk 1b7fd86ec22366ba540a1592a8fd8d054bae57ce # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] gitlabBuilds
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Resolve)
[Pipeline] sh
+ echo Resolve stage
Resolve stage
[Pipeline] updateGitlabCommitStatus
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-011-pipeline/apis
[Pipeline] {
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git@forge.etsi.org:mec/gs011-app-enablement-api.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:mec/gs011-app-enablement-api.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:mec/gs011-app-enablement-api.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse remotes/origin/stf606-draft^{commit} # timeout=10
 > git branch -a -v --no-abbrev --contains 030620d64be5777dab2242490f26e1e8302bb421 # timeout=10
Checking out Revision 030620d64be5777dab2242490f26e1e8302bb421 (origin/stf606-draft)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 030620d64be5777dab2242490f26e1e8302bb421
Commit message: "Update MecAppSupportApi.yaml"
 > git rev-list --no-walk ea2a8aa0e4ff22db521485969d44d9bb5b76713b # timeout=10
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/MEC - Multi-access Edge Computing/mec-gs-011-pipeline/scripts
[Pipeline] {
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/jenkins-scripts-for-openapis.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/stf606-draft, since it originates from another repository
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1b7fd86ec22366ba540a1592a8fd8d054bae57ce (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1b7fd86ec22366ba540a1592a8fd8d054bae57ce
Commit message: "added openapi-cli image version"
[Pipeline] updateGitlabCommitStatus
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Validate)
[Pipeline] updateGitlabCommitStatus
[Pipeline] sh
+ echo Validate stage
Validate stage
[Pipeline] sh
+ bash ./scripts/cli-validate-openapis-mec.sh ./apis

------ Switching to ./apis folder --------
------ Checking for previous logs ------
Found previous log. Removing it
Using dockerized validator (etsiforge/swagger-cli:4.0.3)
4.0.3: Pulling from etsiforge/swagger-cli
Digest: sha256:c6987d82d33715ec65ac79532768eb98152d83ed969754aa7f4a9344aea32d9a
Status: Image is up to date for etsiforge/swagger-cli:4.0.3
docker.io/etsiforge/swagger-cli:4.0.3

------ Validating all YAML files (may takes several minutes) ------

-- Final validator returns 1.
Some errors found, see below the details.

---- Errors detected ----
---- Validating ./MecAppSupportApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecAppSupportApi.yaml... [1] ../specs/MecAppSupportApi.yaml:33:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules/get/summary Operation object `summary` must be non-empty string. 31 | tags: 32 | - appTrafficRules 33 | summary: '' | ^^^^^^^ 34 | description: This method retrieves information about all the traffic rules associated with a MEC application instance. 35 | operationId: ApplicationsTrafficRules_GET Error was generated by the operation-summary rule. [2] ../specs/MecAppSupportApi.yaml:136:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/get/summary Operation object `summary` must be non-empty string. 134 | tags: 135 | - appTrafficRules 136 | summary: '' | ^^^^^^^ 137 | description: This method retrieves information about all the traffic rules associated with a MEC application instance. 138 | operationId: ApplicationsTrafficRule_GET Error was generated by the operation-summary rule. [3] ../specs/MecAppSupportApi.yaml:218:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/put/summary Operation object `summary` must be non-empty string. 216 | tags: 217 | - appTrafficRules 218 | summary: '' | ^^^^^^^ 219 | description: This method retrieves information about all the traffic rules associated with a MEC application instance. 220 | operationId: ApplicationsTrafficRule_PUT Error was generated by the operation-summary rule. [4] ../specs/MecAppSupportApi.yaml:321:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules/get/summary Operation object `summary` must be non-empty string. 319 | tags: 320 | - appDnsRules 321 | summary: '' | ^^^^^^^ 322 | description: This method retrieves information about all the DNS rules associated with a MEC application instance. 323 | operationId: ApplicationsDnsRules_GET Error was generated by the operation-summary rule. [5] ../specs/MecAppSupportApi.yaml:409:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/get/summary Operation object `summary` must be non-empty string. 407 | tags: 408 | - appDnsRules 409 | summary: '' | ^^^^^^^ 410 | description: This method retrieves information about a DNS rule associated with a MEC application instance. 411 | operationId: ApplicationsDnsRule_GET Error was generated by the operation-summary rule. [6] ../specs/MecAppSupportApi.yaml:479:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/put/summary Operation object `summary` must be non-empty string. 477 | tags: 478 | - appDnsRules 479 | summary: '' | ^^^^^^^ 480 | description: This method activates, de-activates or updates a traffic rule. 481 | operationId: ApplicationsDnsRule_PUT Error was generated by the operation-summary rule. [7] ../specs/MecAppSupportApi.yaml:570:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object `summary` must be non-empty string. 568 | tags: 569 | - appSubscriptions 570 | summary: '' | ^^^^^^^ 571 | description: The GET method may be used to request information about all subscriptions for this requestor. Upon success, the response con...<50 chars> 572 | operationId: ApplicationsSubscriptions_GET Error was generated by the operation-summary rule. [8] ../specs/MecAppSupportApi.yaml:624:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object `summary` must be non-empty string. 622 | tags: 623 | - appSubscriptions 624 | summary: '' | ^^^^^^^ 625 | description: The POST method may be used to create a new subscription. One example use case is to create a new subscription to the MEC s...<105 chars> 626 | operationId: ApplicationsSubscriptions_POST Error was generated by the operation-summary rule. [9] ../specs/MecAppSupportApi.yaml:701:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/summary Operation object `summary` must be non-empty string. 699 | tags: 700 | - callbacks 701 | summary: '' | ^^^^^^^ 702 | requestBody: 703 | $ref: '#/components/requestBodies/AppTerminationNotification' Error was generated by the operation-summary rule. [10] ../specs/MecAppSupportApi.yaml:712:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object `summary` must be non-empty string. 710 | tags: 711 | - appSubscriptions 712 | summary: '' | ^^^^^^^ 713 | description: The GET method requests information about a subscription for this requestor. Upon success, the response contains entity body...<28 chars> 714 | operationId: ApplicationsSubscription_GET Error was generated by the operation-summary rule. [11] ../specs/MecAppSupportApi.yaml:773:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object `summary` must be non-empty string. 771 | tags: 772 | - appSubscriptions 773 | summary: '' | ^^^^^^^ 774 | description: This method deletes a mecAppSuptApiSubscription. This method is typically used in "Unsubscribing from service availability e...<17 chars> 775 | operationId: ApplicationsSubscription_DELETE Error was generated by the operation-summary rule. [12] ../specs/MecAppSupportApi.yaml:821:7 at #/paths/~1applications~1{appInstanceId}~1confirm_termination/post/summary Operation object `summary` must be non-empty string. 819 | tags: 820 | - appConfirmTermination 821 | summary: '' | ^^^^^^^ 822 | description: This method is used to confirm the application level termination of an application instance. 823 | operationId: ApplicationsConfirmTermination_POST Error was generated by the operation-summary rule. [13] ../specs/MecAppSupportApi.yaml:905:7 at #/paths/~1applications~1{appInstanceId}~1confirm_ready/post/summary Operation object `summary` must be non-empty string. 903 | tags: 904 | - appConfirmReady 905 | summary: '' | ^^^^^^^ 906 | description: 'This method may be used by the MEC application instance to notify the MEC platform that it is up and running. ' 907 | operationId: ApplicationsConfirmReady_POST Error was generated by the operation-summary rule. [14] ../specs/MecAppSupportApi.yaml:989:7 at #/paths/~1timing~1timing_caps/get/summary Operation object `summary` must be non-empty string. 987 | tags: 988 | - timing 989 | summary: '' | ^^^^^^^ 990 | description: This method retrieves the information of the platform's timing capabilities which corresponds to the timing capabilities query 991 | operationId: TimingCaps_GET Error was generated by the operation-summary rule. [15] ../specs/MecAppSupportApi.yaml:1038:7 at #/paths/~1timing~1current_time/get/summary Operation object `summary` must be non-empty string. 1036 | tags: 1037 | - timing 1038 | summary: '' | ^^^^^^^ 1039 | description: This method retrieves the information of the platform's current time which corresponds to the get platform time procedure 1040 | operationId: TimingCurrentTime_GET Error was generated by the operation-summary rule. [16] ../specs/MecAppSupportApi.yaml:15:3 at #/tags/0/description Tag object should contain `description` field. 13 | url: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf 14 | tags: 15 | - name: appTrafficRules | ^^^^^^^^^^^^^^^^^^^^^ 16 | - name: appDnsRules 17 | - name: appSubscriptions Warning was generated by the tag-description rule. [17] ../specs/MecAppSupportApi.yaml:16:3 at #/tags/1/description Tag object should contain `description` field. 14 | tags: 15 | - name: appTrafficRules 16 | - name: appDnsRules | ^^^^^^^^^^^^^^^^^ 17 | - name: appSubscriptions 18 | - name: appConfirmTermination Warning was generated by the tag-description rule. [18] ../specs/MecAppSupportApi.yaml:17:3 at #/tags/2/description Tag object should contain `description` field. 15 | - name: appTrafficRules 16 | - name: appDnsRules 17 | - name: appSubscriptions | ^^^^^^^^^^^^^^^^^^^^^^ 18 | - name: appConfirmTermination 19 | - name: appConfirmReady Warning was generated by the tag-description rule. [19] ../specs/MecAppSupportApi.yaml:18:3 at #/tags/3/description Tag object should contain `description` field. 16 | - name: appDnsRules 17 | - name: appSubscriptions 18 | - name: appConfirmTermination | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ 19 | - name: appConfirmReady 20 | - name: timing Warning was generated by the tag-description rule. [20] ../specs/MecAppSupportApi.yaml:19:3 at #/tags/4/description Tag object should contain `description` field. 17 | - name: appSubscriptions 18 | - name: appConfirmTermination 19 | - name: appConfirmReady | ^^^^^^^^^^^^^^^^^^^^^ 20 | - name: timing 21 | - name: callbacks Warning was generated by the tag-description rule. [21] ../specs/MecAppSupportApi.yaml:20:3 at #/tags/5/description Tag object should contain `description` field. 18 | - name: appConfirmTermination 19 | - name: appConfirmReady 20 | - name: timing | ^^^^^^^^^^^^ 21 | - name: callbacks 22 | jsonSchemaDialect: https://json-schema.org/draft/2020-12/schema Warning was generated by the tag-description rule. [22] ../specs/MecAppSupportApi.yaml:21:3 at #/tags/6/description Tag object should contain `description` field. 19 | - name: appConfirmReady 20 | - name: timing 21 | - name: callbacks | ^^^^^^^^^^^^^^^ 22 | jsonSchemaDialect: https://json-schema.org/draft/2020-12/schema 23 | servers: Warning was generated by the tag-description rule. [23] ../specs/MecAppSupportApi.yaml:704:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/responses Operation must have at least one `4xx` response. 702 | requestBody: 703 | $ref: '#/components/requestBodies/AppTerminationNotification' 704 | responses: | ^^^^^^^^^ 705 | '200': 706 | description: Expected responses from callback consumer, if it accepts the callback Warning was generated by the operation-4xx-response rule. s/MecAppSupportApi.yaml: validated in 198ms ❌ Validation failed with 15 errors and 8 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.
---- Validating ./MecServiceMgmtApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecServiceMgmtApi.yaml... [1] ../specs/MecServiceMgmtApi.yaml:30:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object should contain `summary` field. 28 | paths: 29 | /applications/{appInstanceId}/subscriptions: 30 | get: | ^^^ 31 | tags: 32 | - appSubscriptions Error was generated by the operation-summary rule. [2] ../specs/MecServiceMgmtApi.yaml:84:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object should contain `summary` field. 82 | contentMediaType: text/plain 83 | deprecated: false 84 | post: | ^^^^ 85 | tags: 86 | - appSubscriptions Error was generated by the operation-summary rule. [3] ../specs/MecServiceMgmtApi.yaml:158:14 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/summary Operation object should contain `summary` field. 156 | ServiceAvailailityNotification: 157 | '{$request.body#/callbackReference}': 158 | post: | ^^^^ 159 | description: >- 160 | 'Represents the service availability information that Error was generated by the operation-summary rule. [4] ../specs/MecServiceMgmtApi.yaml:180:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object should contain `summary` field. 178 | parameters: [] 179 | /applications/{appInstanceId}/subscriptions/{subscriptionId}: 180 | get: | ^^^ 181 | tags: 182 | - appSubscriptions Error was generated by the operation-summary rule. [5] ../specs/MecServiceMgmtApi.yaml:241:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object should contain `summary` field. 239 | contentMediaType: text/plain 240 | deprecated: false 241 | delete: | ^^^^^^ 242 | tags: 243 | - appSubscriptions Error was generated by the operation-summary rule. [6] ../specs/MecServiceMgmtApi.yaml:289:5 at #/paths/~1applications~1{appInstanceId}~1services/get/summary Operation object should contain `summary` field. 287 | parameters: [] 288 | /applications/{appInstanceId}/services: 289 | get: | ^^^ 290 | tags: 291 | - appServices Error was generated by the operation-summary rule. [7] ../specs/MecServiceMgmtApi.yaml:460:5 at #/paths/~1applications~1{appInstanceId}~1services/post/summary Operation object should contain `summary` field. 458 | contentMediaType: text/plain 459 | deprecated: false 460 | post: | ^^^^ 461 | tags: 462 | - appServices Error was generated by the operation-summary rule. [8] ../specs/MecServiceMgmtApi.yaml:562:5 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 560 | parameters: [] 561 | /applications/{appInstanceId}/services/{serviceId}: 562 | get: | ^^^ 563 | tags: 564 | - appServices Error was generated by the operation-summary rule. [9] ../specs/MecServiceMgmtApi.yaml:650:5 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/put/summary Operation object should contain `summary` field. 648 | contentMediaType: text/plain 649 | deprecated: false 650 | put: | ^^^ 651 | tags: 652 | - appServices Error was generated by the operation-summary rule. [10] ../specs/MecServiceMgmtApi.yaml:757:5 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/delete/summary Operation object should contain `summary` field. 755 | contentMediaType: text/plain 756 | deprecated: false 757 | delete: | ^^^^^^ 758 | tags: 759 | - appServices Error was generated by the operation-summary rule. [11] ../specs/MecServiceMgmtApi.yaml:804:5 at #/paths/~1services/get/summary Operation object should contain `summary` field. 802 | parameters: [] 803 | /services: 804 | get: | ^^^ 805 | tags: 806 | - services Error was generated by the operation-summary rule. [12] ../specs/MecServiceMgmtApi.yaml:971:5 at #/paths/~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 969 | parameters: [] 970 | /services/{serviceId}: 971 | get: | ^^^ 972 | tags: 973 | - services Error was generated by the operation-summary rule. [13] ../specs/MecServiceMgmtApi.yaml:1055:5 at #/paths/~1transports/get/summary Operation object should contain `summary` field. 1053 | parameters: [] 1054 | /transports: 1055 | get: | ^^^ 1056 | tags: 1057 | - transports Error was generated by the operation-summary rule. [14] ../specs/MecServiceMgmtApi.yaml:1109:5 at #/paths/~1resource_uri_allocated_by_MEC_platform/get/summary Operation object should contain `summary` field. 1107 | 1108 | /resource_uri_allocated_by_MEC_platform: 1109 | get: | ^^^ 1110 | tags: 1111 | - individualMECservice Error was generated by the operation-summary rule. [15] ../specs/MecServiceMgmtApi.yaml:1140:5 at #/paths/~1resource_uri_allocated_by_MEC_platform/patch/summary Operation object should contain `summary` field. 1138 | schema: 1139 | $ref: '#/components/schemas/ProblemDetails' 1140 | patch: | ^^^^^ 1141 | tags: 1142 | - individualMECservice Error was generated by the operation-summary rule. [16] ../specs/MecServiceMgmtApi.yaml:21:3 at #/tags/0/description Tag object should contain `description` field. 19 | variables: {} 20 | tags: 21 | - name: appSubscriptions | ^^^^^^^^^^^^^^^^^^^^^^ 22 | - name: appServices 23 | - name: services Warning was generated by the tag-description rule. [17] ../specs/MecServiceMgmtApi.yaml:22:3 at #/tags/1/description Tag object should contain `description` field. 20 | tags: 21 | - name: appSubscriptions 22 | - name: appServices | ^^^^^^^^^^^^^^^^^ 23 | - name: services 24 | - name: transports Warning was generated by the tag-description rule. [18] ../specs/MecServiceMgmtApi.yaml:23:3 at #/tags/2/description Tag object should contain `description` field. 21 | - name: appSubscriptions 22 | - name: appServices 23 | - name: services | ^^^^^^^^^^^^^^ 24 | - name: transports 25 | - name: callbacks Warning was generated by the tag-description rule. [19] ../specs/MecServiceMgmtApi.yaml:24:3 at #/tags/3/description Tag object should contain `description` field. 22 | - name: appServices 23 | - name: services 24 | - name: transports | ^^^^^^^^^^^^^^^^ 25 | - name: callbacks 26 | - name: individualMECservice Warning was generated by the tag-description rule. [20] ../specs/MecServiceMgmtApi.yaml:25:3 at #/tags/4/description Tag object should contain `description` field. 23 | - name: services 24 | - name: transports 25 | - name: callbacks | ^^^^^^^^^^^^^^^ 26 | - name: individualMECservice 27 | Warning was generated by the tag-description rule. [21] ../specs/MecServiceMgmtApi.yaml:26:3 at #/tags/5/description Tag object should contain `description` field. 24 | - name: transports 25 | - name: callbacks 26 | - name: individualMECservice | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 27 | 28 | paths: Warning was generated by the tag-description rule. [22] ../specs/MecServiceMgmtApi.yaml:175:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 173 | requestBody: 174 | $ref: '#/components/requestBodies/ServiceAvailabilityNotification' 175 | responses: | ^^^^^^^^^ 176 | '200': 177 | description: Expected responses from callback consumer, if it accepts the callback Warning was generated by the operation-4xx-response rule. s/MecServiceMgmtApi.yaml: validated in 217ms ❌ Validation failed with 15 errors and 7 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.
---- Validating ./MecAppSupportApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecAppSupportApi.json... [1] ../specs/MecAppSupportApi.json:55:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules/get/summary Operation object should contain `summary` field. 53 | "paths": { 54 | "/applications/{appInstanceId}/traffic_rules": { 55 | "get": { | ^^^^^ 56 | "tags": [ 57 | "appTrafficRules" Error was generated by the operation-summary rule. [2] ../specs/MecAppSupportApi.json:216:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/get/summary Operation object should contain `summary` field. 214 | }, 215 | "/applications/{appInstanceId}/traffic_rules/{trafficRuleId}": { 216 | "get": { | ^^^^^ 217 | "tags": [ 218 | "appTrafficRules" Error was generated by the operation-summary rule. [3] ../specs/MecAppSupportApi.json:339:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/put/summary Operation object should contain `summary` field. 337 | "deprecated": false 338 | }, 339 | "put": { | ^^^^^ 340 | "tags": [ 341 | "appTrafficRules" Error was generated by the operation-summary rule. [4] ../specs/MecAppSupportApi.json:494:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules/get/summary Operation object should contain `summary` field. 492 | }, 493 | "/applications/{appInstanceId}/dns_rules": { 494 | "get": { | ^^^^^ 495 | "tags": [ 496 | "appDnsRules" Error was generated by the operation-summary rule. [5] ../specs/MecAppSupportApi.json:624:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/get/summary Operation object should contain `summary` field. 622 | }, 623 | "/applications/{appInstanceId}/dns_rules/{dnsRuleId}": { 624 | "get": { | ^^^^^ 625 | "tags": [ 626 | "appDnsRules" Error was generated by the operation-summary rule. [6] ../specs/MecAppSupportApi.json:726:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/put/summary Operation object should contain `summary` field. 724 | "deprecated": false 725 | }, 726 | "put": { | ^^^^^ 727 | "tags": [ 728 | "appDnsRules" Error was generated by the operation-summary rule. [7] ../specs/MecAppSupportApi.json:860:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object should contain `summary` field. 858 | }, 859 | "/applications/{appInstanceId}/subscriptions": { 860 | "get": { | ^^^^^ 861 | "tags": [ 862 | "appSubscriptions" Error was generated by the operation-summary rule. [8] ../specs/MecAppSupportApi.json:940:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object should contain `summary` field. 938 | "deprecated": false 939 | }, 940 | "post": { | ^^^^^^ 941 | "tags": [ 942 | "appSubscriptions" Error was generated by the operation-summary rule. [9] ../specs/MecAppSupportApi.json:1046:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/summary Operation object should contain `summary` field. 1044 | "AppTerminationNotification": { 1045 | "{$request.body#/callbackUri}": { 1046 | "post": { | ^^^^^^ 1047 | "description": "Represents the information that the MEP notifies the subscribed application instance about the corresponding applic...<21 chars> 1048 | "operationId": "AppTerminationNotification_POST", Error was generated by the operation-summary rule. [10] ../specs/MecAppSupportApi.json:1068:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object should contain `summary` field. 1066 | }, 1067 | "/applications/{appInstanceId}/subscriptions/{subscriptionId}": { 1068 | "get": { | ^^^^^ 1069 | "tags": [ 1070 | "appSubscriptions" Error was generated by the operation-summary rule. [11] ../specs/MecAppSupportApi.json:1158:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object should contain `summary` field. 1156 | "deprecated": false 1157 | }, 1158 | "delete": { | ^^^^^^^^ 1159 | "tags": [ 1160 | "appSubscriptions" Error was generated by the operation-summary rule. [12] ../specs/MecAppSupportApi.json:1227:7 at #/paths/~1applications~1{appInstanceId}~1confirm_termination/post/summary Operation object should contain `summary` field. 1225 | }, 1226 | "/applications/{appInstanceId}/confirm_termination": { 1227 | "post": { | ^^^^^^ 1228 | "tags": [ 1229 | "appConfirmTermination" Error was generated by the operation-summary rule. [13] ../specs/MecAppSupportApi.json:1351:7 at #/paths/~1applications~1{appInstanceId}~1confirm_ready/post/summary Operation object should contain `summary` field. 1349 | }, 1350 | "/applications/{appInstanceId}/confirm_ready": { 1351 | "post": { | ^^^^^^ 1352 | "tags": [ 1353 | "appConfirmReady" Error was generated by the operation-summary rule. [14] ../specs/MecAppSupportApi.json:1475:7 at #/paths/~1timing~1timing_caps/get/summary Operation object should contain `summary` field. 1473 | }, 1474 | "/timing/timing_caps": { 1475 | "get": { | ^^^^^ 1476 | "tags": [ 1477 | "timing" Error was generated by the operation-summary rule. [15] ../specs/MecAppSupportApi.json:1547:7 at #/paths/~1timing~1current_time/get/summary Operation object should contain `summary` field. 1545 | }, 1546 | "/timing/current_time": { 1547 | "get": { | ^^^^^ 1548 | "tags": [ 1549 | "timing" Error was generated by the operation-summary rule. [16] ../specs/MecAppSupportApi.json:20:5 at #/tags/0/description Tag object should contain `description` field. 18 | }, 19 | "tags": [ 20 | { | ^ 21 | "name": "appTrafficRules" | ^^^^^^^^^^^^^^^^^^^^^^^^^ 22 | }, | ^ 23 | { 24 | "name": "appDnsRules" Warning was generated by the tag-description rule. [17] ../specs/MecAppSupportApi.json:23:5 at #/tags/1/description Tag object should contain `description` field. 21 | "name": "appTrafficRules" 22 | }, 23 | { | ^ 24 | "name": "appDnsRules" | ^^^^^^^^^^^^^^^^^^^^^ 25 | }, | ^ 26 | { 27 | "name": "appSubscriptions" Warning was generated by the tag-description rule. [18] ../specs/MecAppSupportApi.json:26:5 at #/tags/2/description Tag object should contain `description` field. 24 | "name": "appDnsRules" 25 | }, 26 | { | ^ 27 | "name": "appSubscriptions" | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 28 | }, | ^ 29 | { 30 | "name": "appConfirmTermination" Warning was generated by the tag-description rule. [19] ../specs/MecAppSupportApi.json:29:5 at #/tags/3/description Tag object should contain `description` field. 27 | "name": "appSubscriptions" 28 | }, 29 | { | ^ 30 | "name": "appConfirmTermination" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 31 | }, | ^ 32 | { 33 | "name": "appConfirmReady" Warning was generated by the tag-description rule. [20] ../specs/MecAppSupportApi.json:32:5 at #/tags/4/description Tag object should contain `description` field. 30 | "name": "appConfirmTermination" 31 | }, 32 | { | ^ 33 | "name": "appConfirmReady" | ^^^^^^^^^^^^^^^^^^^^^^^^^ 34 | }, | ^ 35 | { 36 | "name": "timing" Warning was generated by the tag-description rule. [21] ../specs/MecAppSupportApi.json:35:5 at #/tags/5/description Tag object should contain `description` field. 33 | "name": "appConfirmReady" 34 | }, 35 | { | ^ 36 | "name": "timing" | ^^^^^^^^^^^^^^^^ 37 | }, | ^ 38 | { 39 | "name": "callbacks" Warning was generated by the tag-description rule. [22] ../specs/MecAppSupportApi.json:38:5 at #/tags/6/description Tag object should contain `description` field. 36 | "name": "timing" 37 | }, 38 | { | ^ 39 | "name": "callbacks" | ^^^^^^^^^^^^^^^^^^^ 40 | } | ^ 41 | ], 42 | "jsonSchemaDialect": "https://json-schema.org/draft/2020-12/schema", Warning was generated by the tag-description rule. [23] ../specs/MecAppSupportApi.json:1055:17 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/responses Operation must have at least one `4xx` response. 1053 | "$ref": "#/components/requestBodies/AppTerminationNotification" 1054 | }, 1055 | "responses": { | ^^^^^^^^^^^ 1056 | "200": { 1057 | "description": "Expected responses from callback consumer, if it accepts the callback" Warning was generated by the operation-4xx-response rule. s/MecAppSupportApi.json: validated in 197ms ❌ Validation failed with 15 errors and 8 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.
---- Validating ./MecServiceMgmtApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecServiceMgmtApi.json... [1] ../specs/MecServiceMgmtApi.json:52:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object should contain `summary` field. 50 | "paths": { 51 | "/applications/{appInstanceId}/subscriptions": { 52 | "get": { | ^^^^^ 53 | "tags": [ 54 | "appSubscriptions" Error was generated by the operation-summary rule. [2] ../specs/MecServiceMgmtApi.json:132:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object should contain `summary` field. 130 | "deprecated": false 131 | }, 132 | "post": { | ^^^^^^ 133 | "tags": [ 134 | "appSubscriptions" Error was generated by the operation-summary rule. [3] ../specs/MecServiceMgmtApi.json:238:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/summary Operation object should contain `summary` field. 236 | "ServiceAvailailityNotification": { 237 | "{$request.body#/callbackReference}": { 238 | "post": { | ^^^^^^ 239 | "description": "'Represents the service availability information that is used in the following cases
 when the MEC platform anno...<416 chars> 240 | "operationId": "ServiceAvailabilityNotification_POST", Error was generated by the operation-summary rule. [4] ../specs/MecServiceMgmtApi.json:260:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object should contain `summary` field. 258 | }, 259 | "/applications/{appInstanceId}/subscriptions/{subscriptionId}": { 260 | "get": { | ^^^^^ 261 | "tags": [ 262 | "appSubscriptions" Error was generated by the operation-summary rule. [5] ../specs/MecServiceMgmtApi.json:350:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object should contain `summary` field. 348 | "deprecated": false 349 | }, 350 | "delete": { | ^^^^^^^^ 351 | "tags": [ 352 | "appSubscriptions" Error was generated by the operation-summary rule. [6] ../specs/MecServiceMgmtApi.json:419:7 at #/paths/~1applications~1{appInstanceId}~1services/get/summary Operation object should contain `summary` field. 417 | }, 418 | "/applications/{appInstanceId}/services": { 419 | "get": { | ^^^^^ 420 | "tags": [ 421 | "appServices" Error was generated by the operation-summary rule. [7] ../specs/MecServiceMgmtApi.json:672:7 at #/paths/~1applications~1{appInstanceId}~1services/post/summary Operation object should contain `summary` field. 670 | "deprecated": false 671 | }, 672 | "post": { | ^^^^^^ 673 | "tags": [ 674 | "appServices" Error was generated by the operation-summary rule. [8] ../specs/MecServiceMgmtApi.json:826:7 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 824 | }, 825 | "/applications/{appInstanceId}/services/{serviceId}": { 826 | "get": { | ^^^^^ 827 | "tags": [ 828 | "appServices" Error was generated by the operation-summary rule. [9] ../specs/MecServiceMgmtApi.json:954:7 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/put/summary Operation object should contain `summary` field. 952 | "deprecated": false 953 | }, 954 | "put": { | ^^^^^ 955 | "tags": [ 956 | "appServices" Error was generated by the operation-summary rule. [10] ../specs/MecServiceMgmtApi.json:1111:7 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/delete/summary Operation object should contain `summary` field. 1109 | "deprecated": false 1110 | }, 1111 | "delete": { | ^^^^^^^^ 1112 | "tags": [ 1113 | "appServices" Error was generated by the operation-summary rule. [11] ../specs/MecServiceMgmtApi.json:1180:7 at #/paths/~1services/get/summary Operation object should contain `summary` field. 1178 | }, 1179 | "/services": { 1180 | "get": { | ^^^^^ 1181 | "tags": [ 1182 | "services" Error was generated by the operation-summary rule. [12] ../specs/MecServiceMgmtApi.json:1426:7 at #/paths/~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 1424 | }, 1425 | "/services/{serviceId}": { 1426 | "get": { | ^^^^^ 1427 | "tags": [ 1428 | "services" Error was generated by the operation-summary rule. [13] ../specs/MecServiceMgmtApi.json:1547:7 at #/paths/~1transports/get/summary Operation object should contain `summary` field. 1545 | }, 1546 | "/transports": { 1547 | "get": { | ^^^^^ 1548 | "tags": [ 1549 | "transports" Error was generated by the operation-summary rule. [14] ../specs/MecServiceMgmtApi.json:1624:7 at #/paths/~1resource_uri_allocated_by_MEC_platform/get/summary Operation object should contain `summary` field. 1622 | }, 1623 | "/resource_uri_allocated_by_MEC_platform": { 1624 | "get": { | ^^^^^ 1625 | "tags": [ 1626 | "individualMECservice" Error was generated by the operation-summary rule. [15] ../specs/MecServiceMgmtApi.json:1673:7 at #/paths/~1resource_uri_allocated_by_MEC_platform/patch/summary Operation object should contain `summary` field. 1671 | } 1672 | }, 1673 | "patch": { | ^^^^^^^ 1674 | "tags": [ 1675 | "individualMECservice" Error was generated by the operation-summary rule. [16] ../specs/MecServiceMgmtApi.json:31:5 at #/tags/0/description Tag object should contain `description` field. 29 | ], 30 | "tags": [ 31 | { | ^ 32 | "name": "appSubscriptions" | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 33 | }, | ^ 34 | { 35 | "name": "appServices" Warning was generated by the tag-description rule. [17] ../specs/MecServiceMgmtApi.json:34:5 at #/tags/1/description Tag object should contain `description` field. 32 | "name": "appSubscriptions" 33 | }, 34 | { | ^ 35 | "name": "appServices" | ^^^^^^^^^^^^^^^^^^^^^ 36 | }, | ^ 37 | { 38 | "name": "services" Warning was generated by the tag-description rule. [18] ../specs/MecServiceMgmtApi.json:37:5 at #/tags/2/description Tag object should contain `description` field. 35 | "name": "appServices" 36 | }, 37 | { | ^ 38 | "name": "services" | ^^^^^^^^^^^^^^^^^^ 39 | }, | ^ 40 | { 41 | "name": "transports" Warning was generated by the tag-description rule. [19] ../specs/MecServiceMgmtApi.json:40:5 at #/tags/3/description Tag object should contain `description` field. 38 | "name": "services" 39 | }, 40 | { | ^ 41 | "name": "transports" | ^^^^^^^^^^^^^^^^^^^^ 42 | }, | ^ 43 | { 44 | "name": "callbacks" Warning was generated by the tag-description rule. [20] ../specs/MecServiceMgmtApi.json:43:5 at #/tags/4/description Tag object should contain `description` field. 41 | "name": "transports" 42 | }, 43 | { | ^ 44 | "name": "callbacks" | ^^^^^^^^^^^^^^^^^^^ 45 | }, | ^ 46 | { 47 | "name": "individualMECservice" Warning was generated by the tag-description rule. [21] ../specs/MecServiceMgmtApi.json:46:5 at #/tags/5/description Tag object should contain `description` field. 44 | "name": "callbacks" 45 | }, 46 | { | ^ 47 | "name": "individualMECservice" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 48 | } | ^ 49 | ], 50 | "paths": { Warning was generated by the tag-description rule. [22] ../specs/MecServiceMgmtApi.json:247:17 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 245 | "$ref": "#/components/requestBodies/ServiceAvailabilityNotification" 246 | }, 247 | "responses": { | ^^^^^^^^^^^ 248 | "200": { 249 | "description": "Expected responses from callback consumer, if it accepts the callback" Warning was generated by the operation-4xx-response rule. s/MecServiceMgmtApi.json: validated in 194ms ❌ Validation failed with 15 errors and 7 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.


---- Complete log of validation ----
---- Validating ./MecAppSupportApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecAppSupportApi.yaml... [1] ../specs/MecAppSupportApi.yaml:33:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules/get/summary Operation object `summary` must be non-empty string. 31 | tags: 32 | - appTrafficRules 33 | summary: '' | ^^^^^^^ 34 | description: This method retrieves information about all the traffic rules associated with a MEC application instance. 35 | operationId: ApplicationsTrafficRules_GET Error was generated by the operation-summary rule. [2] ../specs/MecAppSupportApi.yaml:136:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/get/summary Operation object `summary` must be non-empty string. 134 | tags: 135 | - appTrafficRules 136 | summary: '' | ^^^^^^^ 137 | description: This method retrieves information about all the traffic rules associated with a MEC application instance. 138 | operationId: ApplicationsTrafficRule_GET Error was generated by the operation-summary rule. [3] ../specs/MecAppSupportApi.yaml:218:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/put/summary Operation object `summary` must be non-empty string. 216 | tags: 217 | - appTrafficRules 218 | summary: '' | ^^^^^^^ 219 | description: This method retrieves information about all the traffic rules associated with a MEC application instance. 220 | operationId: ApplicationsTrafficRule_PUT Error was generated by the operation-summary rule. [4] ../specs/MecAppSupportApi.yaml:321:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules/get/summary Operation object `summary` must be non-empty string. 319 | tags: 320 | - appDnsRules 321 | summary: '' | ^^^^^^^ 322 | description: This method retrieves information about all the DNS rules associated with a MEC application instance. 323 | operationId: ApplicationsDnsRules_GET Error was generated by the operation-summary rule. [5] ../specs/MecAppSupportApi.yaml:409:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/get/summary Operation object `summary` must be non-empty string. 407 | tags: 408 | - appDnsRules 409 | summary: '' | ^^^^^^^ 410 | description: This method retrieves information about a DNS rule associated with a MEC application instance. 411 | operationId: ApplicationsDnsRule_GET Error was generated by the operation-summary rule. [6] ../specs/MecAppSupportApi.yaml:479:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/put/summary Operation object `summary` must be non-empty string. 477 | tags: 478 | - appDnsRules 479 | summary: '' | ^^^^^^^ 480 | description: This method activates, de-activates or updates a traffic rule. 481 | operationId: ApplicationsDnsRule_PUT Error was generated by the operation-summary rule. [7] ../specs/MecAppSupportApi.yaml:570:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object `summary` must be non-empty string. 568 | tags: 569 | - appSubscriptions 570 | summary: '' | ^^^^^^^ 571 | description: The GET method may be used to request information about all subscriptions for this requestor. Upon success, the response con...<50 chars> 572 | operationId: ApplicationsSubscriptions_GET Error was generated by the operation-summary rule. [8] ../specs/MecAppSupportApi.yaml:624:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object `summary` must be non-empty string. 622 | tags: 623 | - appSubscriptions 624 | summary: '' | ^^^^^^^ 625 | description: The POST method may be used to create a new subscription. One example use case is to create a new subscription to the MEC s...<105 chars> 626 | operationId: ApplicationsSubscriptions_POST Error was generated by the operation-summary rule. [9] ../specs/MecAppSupportApi.yaml:701:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/summary Operation object `summary` must be non-empty string. 699 | tags: 700 | - callbacks 701 | summary: '' | ^^^^^^^ 702 | requestBody: 703 | $ref: '#/components/requestBodies/AppTerminationNotification' Error was generated by the operation-summary rule. [10] ../specs/MecAppSupportApi.yaml:712:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object `summary` must be non-empty string. 710 | tags: 711 | - appSubscriptions 712 | summary: '' | ^^^^^^^ 713 | description: The GET method requests information about a subscription for this requestor. Upon success, the response contains entity body...<28 chars> 714 | operationId: ApplicationsSubscription_GET Error was generated by the operation-summary rule. [11] ../specs/MecAppSupportApi.yaml:773:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object `summary` must be non-empty string. 771 | tags: 772 | - appSubscriptions 773 | summary: '' | ^^^^^^^ 774 | description: This method deletes a mecAppSuptApiSubscription. This method is typically used in "Unsubscribing from service availability e...<17 chars> 775 | operationId: ApplicationsSubscription_DELETE Error was generated by the operation-summary rule. [12] ../specs/MecAppSupportApi.yaml:821:7 at #/paths/~1applications~1{appInstanceId}~1confirm_termination/post/summary Operation object `summary` must be non-empty string. 819 | tags: 820 | - appConfirmTermination 821 | summary: '' | ^^^^^^^ 822 | description: This method is used to confirm the application level termination of an application instance. 823 | operationId: ApplicationsConfirmTermination_POST Error was generated by the operation-summary rule. [13] ../specs/MecAppSupportApi.yaml:905:7 at #/paths/~1applications~1{appInstanceId}~1confirm_ready/post/summary Operation object `summary` must be non-empty string. 903 | tags: 904 | - appConfirmReady 905 | summary: '' | ^^^^^^^ 906 | description: 'This method may be used by the MEC application instance to notify the MEC platform that it is up and running. ' 907 | operationId: ApplicationsConfirmReady_POST Error was generated by the operation-summary rule. [14] ../specs/MecAppSupportApi.yaml:989:7 at #/paths/~1timing~1timing_caps/get/summary Operation object `summary` must be non-empty string. 987 | tags: 988 | - timing 989 | summary: '' | ^^^^^^^ 990 | description: This method retrieves the information of the platform's timing capabilities which corresponds to the timing capabilities query 991 | operationId: TimingCaps_GET Error was generated by the operation-summary rule. [15] ../specs/MecAppSupportApi.yaml:1038:7 at #/paths/~1timing~1current_time/get/summary Operation object `summary` must be non-empty string. 1036 | tags: 1037 | - timing 1038 | summary: '' | ^^^^^^^ 1039 | description: This method retrieves the information of the platform's current time which corresponds to the get platform time procedure 1040 | operationId: TimingCurrentTime_GET Error was generated by the operation-summary rule. [16] ../specs/MecAppSupportApi.yaml:15:3 at #/tags/0/description Tag object should contain `description` field. 13 | url: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf 14 | tags: 15 | - name: appTrafficRules | ^^^^^^^^^^^^^^^^^^^^^ 16 | - name: appDnsRules 17 | - name: appSubscriptions Warning was generated by the tag-description rule. [17] ../specs/MecAppSupportApi.yaml:16:3 at #/tags/1/description Tag object should contain `description` field. 14 | tags: 15 | - name: appTrafficRules 16 | - name: appDnsRules | ^^^^^^^^^^^^^^^^^ 17 | - name: appSubscriptions 18 | - name: appConfirmTermination Warning was generated by the tag-description rule. [18] ../specs/MecAppSupportApi.yaml:17:3 at #/tags/2/description Tag object should contain `description` field. 15 | - name: appTrafficRules 16 | - name: appDnsRules 17 | - name: appSubscriptions | ^^^^^^^^^^^^^^^^^^^^^^ 18 | - name: appConfirmTermination 19 | - name: appConfirmReady Warning was generated by the tag-description rule. [19] ../specs/MecAppSupportApi.yaml:18:3 at #/tags/3/description Tag object should contain `description` field. 16 | - name: appDnsRules 17 | - name: appSubscriptions 18 | - name: appConfirmTermination | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ 19 | - name: appConfirmReady 20 | - name: timing Warning was generated by the tag-description rule. [20] ../specs/MecAppSupportApi.yaml:19:3 at #/tags/4/description Tag object should contain `description` field. 17 | - name: appSubscriptions 18 | - name: appConfirmTermination 19 | - name: appConfirmReady | ^^^^^^^^^^^^^^^^^^^^^ 20 | - name: timing 21 | - name: callbacks Warning was generated by the tag-description rule. [21] ../specs/MecAppSupportApi.yaml:20:3 at #/tags/5/description Tag object should contain `description` field. 18 | - name: appConfirmTermination 19 | - name: appConfirmReady 20 | - name: timing | ^^^^^^^^^^^^ 21 | - name: callbacks 22 | jsonSchemaDialect: https://json-schema.org/draft/2020-12/schema Warning was generated by the tag-description rule. [22] ../specs/MecAppSupportApi.yaml:21:3 at #/tags/6/description Tag object should contain `description` field. 19 | - name: appConfirmReady 20 | - name: timing 21 | - name: callbacks | ^^^^^^^^^^^^^^^ 22 | jsonSchemaDialect: https://json-schema.org/draft/2020-12/schema 23 | servers: Warning was generated by the tag-description rule. [23] ../specs/MecAppSupportApi.yaml:704:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/responses Operation must have at least one `4xx` response. 702 | requestBody: 703 | $ref: '#/components/requestBodies/AppTerminationNotification' 704 | responses: | ^^^^^^^^^ 705 | '200': 706 | description: Expected responses from callback consumer, if it accepts the callback Warning was generated by the operation-4xx-response rule. s/MecAppSupportApi.yaml: validated in 198ms ❌ Validation failed with 15 errors and 8 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.
---- Validating ./MecServiceMgmtApi.yaml: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecServiceMgmtApi.yaml... [1] ../specs/MecServiceMgmtApi.yaml:30:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object should contain `summary` field. 28 | paths: 29 | /applications/{appInstanceId}/subscriptions: 30 | get: | ^^^ 31 | tags: 32 | - appSubscriptions Error was generated by the operation-summary rule. [2] ../specs/MecServiceMgmtApi.yaml:84:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object should contain `summary` field. 82 | contentMediaType: text/plain 83 | deprecated: false 84 | post: | ^^^^ 85 | tags: 86 | - appSubscriptions Error was generated by the operation-summary rule. [3] ../specs/MecServiceMgmtApi.yaml:158:14 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/summary Operation object should contain `summary` field. 156 | ServiceAvailailityNotification: 157 | '{$request.body#/callbackReference}': 158 | post: | ^^^^ 159 | description: >- 160 | 'Represents the service availability information that Error was generated by the operation-summary rule. [4] ../specs/MecServiceMgmtApi.yaml:180:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object should contain `summary` field. 178 | parameters: [] 179 | /applications/{appInstanceId}/subscriptions/{subscriptionId}: 180 | get: | ^^^ 181 | tags: 182 | - appSubscriptions Error was generated by the operation-summary rule. [5] ../specs/MecServiceMgmtApi.yaml:241:5 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object should contain `summary` field. 239 | contentMediaType: text/plain 240 | deprecated: false 241 | delete: | ^^^^^^ 242 | tags: 243 | - appSubscriptions Error was generated by the operation-summary rule. [6] ../specs/MecServiceMgmtApi.yaml:289:5 at #/paths/~1applications~1{appInstanceId}~1services/get/summary Operation object should contain `summary` field. 287 | parameters: [] 288 | /applications/{appInstanceId}/services: 289 | get: | ^^^ 290 | tags: 291 | - appServices Error was generated by the operation-summary rule. [7] ../specs/MecServiceMgmtApi.yaml:460:5 at #/paths/~1applications~1{appInstanceId}~1services/post/summary Operation object should contain `summary` field. 458 | contentMediaType: text/plain 459 | deprecated: false 460 | post: | ^^^^ 461 | tags: 462 | - appServices Error was generated by the operation-summary rule. [8] ../specs/MecServiceMgmtApi.yaml:562:5 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 560 | parameters: [] 561 | /applications/{appInstanceId}/services/{serviceId}: 562 | get: | ^^^ 563 | tags: 564 | - appServices Error was generated by the operation-summary rule. [9] ../specs/MecServiceMgmtApi.yaml:650:5 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/put/summary Operation object should contain `summary` field. 648 | contentMediaType: text/plain 649 | deprecated: false 650 | put: | ^^^ 651 | tags: 652 | - appServices Error was generated by the operation-summary rule. [10] ../specs/MecServiceMgmtApi.yaml:757:5 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/delete/summary Operation object should contain `summary` field. 755 | contentMediaType: text/plain 756 | deprecated: false 757 | delete: | ^^^^^^ 758 | tags: 759 | - appServices Error was generated by the operation-summary rule. [11] ../specs/MecServiceMgmtApi.yaml:804:5 at #/paths/~1services/get/summary Operation object should contain `summary` field. 802 | parameters: [] 803 | /services: 804 | get: | ^^^ 805 | tags: 806 | - services Error was generated by the operation-summary rule. [12] ../specs/MecServiceMgmtApi.yaml:971:5 at #/paths/~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 969 | parameters: [] 970 | /services/{serviceId}: 971 | get: | ^^^ 972 | tags: 973 | - services Error was generated by the operation-summary rule. [13] ../specs/MecServiceMgmtApi.yaml:1055:5 at #/paths/~1transports/get/summary Operation object should contain `summary` field. 1053 | parameters: [] 1054 | /transports: 1055 | get: | ^^^ 1056 | tags: 1057 | - transports Error was generated by the operation-summary rule. [14] ../specs/MecServiceMgmtApi.yaml:1109:5 at #/paths/~1resource_uri_allocated_by_MEC_platform/get/summary Operation object should contain `summary` field. 1107 | 1108 | /resource_uri_allocated_by_MEC_platform: 1109 | get: | ^^^ 1110 | tags: 1111 | - individualMECservice Error was generated by the operation-summary rule. [15] ../specs/MecServiceMgmtApi.yaml:1140:5 at #/paths/~1resource_uri_allocated_by_MEC_platform/patch/summary Operation object should contain `summary` field. 1138 | schema: 1139 | $ref: '#/components/schemas/ProblemDetails' 1140 | patch: | ^^^^^ 1141 | tags: 1142 | - individualMECservice Error was generated by the operation-summary rule. [16] ../specs/MecServiceMgmtApi.yaml:21:3 at #/tags/0/description Tag object should contain `description` field. 19 | variables: {} 20 | tags: 21 | - name: appSubscriptions | ^^^^^^^^^^^^^^^^^^^^^^ 22 | - name: appServices 23 | - name: services Warning was generated by the tag-description rule. [17] ../specs/MecServiceMgmtApi.yaml:22:3 at #/tags/1/description Tag object should contain `description` field. 20 | tags: 21 | - name: appSubscriptions 22 | - name: appServices | ^^^^^^^^^^^^^^^^^ 23 | - name: services 24 | - name: transports Warning was generated by the tag-description rule. [18] ../specs/MecServiceMgmtApi.yaml:23:3 at #/tags/2/description Tag object should contain `description` field. 21 | - name: appSubscriptions 22 | - name: appServices 23 | - name: services | ^^^^^^^^^^^^^^ 24 | - name: transports 25 | - name: callbacks Warning was generated by the tag-description rule. [19] ../specs/MecServiceMgmtApi.yaml:24:3 at #/tags/3/description Tag object should contain `description` field. 22 | - name: appServices 23 | - name: services 24 | - name: transports | ^^^^^^^^^^^^^^^^ 25 | - name: callbacks 26 | - name: individualMECservice Warning was generated by the tag-description rule. [20] ../specs/MecServiceMgmtApi.yaml:25:3 at #/tags/4/description Tag object should contain `description` field. 23 | - name: services 24 | - name: transports 25 | - name: callbacks | ^^^^^^^^^^^^^^^ 26 | - name: individualMECservice 27 | Warning was generated by the tag-description rule. [21] ../specs/MecServiceMgmtApi.yaml:26:3 at #/tags/5/description Tag object should contain `description` field. 24 | - name: transports 25 | - name: callbacks 26 | - name: individualMECservice | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 27 | 28 | paths: Warning was generated by the tag-description rule. [22] ../specs/MecServiceMgmtApi.yaml:175:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 173 | requestBody: 174 | $ref: '#/components/requestBodies/ServiceAvailabilityNotification' 175 | responses: | ^^^^^^^^^ 176 | '200': 177 | description: Expected responses from callback consumer, if it accepts the callback Warning was generated by the operation-4xx-response rule. s/MecServiceMgmtApi.yaml: validated in 217ms ❌ Validation failed with 15 errors and 7 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.
---- Validating ./MecAppSupportApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecAppSupportApi.json... [1] ../specs/MecAppSupportApi.json:55:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules/get/summary Operation object should contain `summary` field. 53 | "paths": { 54 | "/applications/{appInstanceId}/traffic_rules": { 55 | "get": { | ^^^^^ 56 | "tags": [ 57 | "appTrafficRules" Error was generated by the operation-summary rule. [2] ../specs/MecAppSupportApi.json:216:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/get/summary Operation object should contain `summary` field. 214 | }, 215 | "/applications/{appInstanceId}/traffic_rules/{trafficRuleId}": { 216 | "get": { | ^^^^^ 217 | "tags": [ 218 | "appTrafficRules" Error was generated by the operation-summary rule. [3] ../specs/MecAppSupportApi.json:339:7 at #/paths/~1applications~1{appInstanceId}~1traffic_rules~1{trafficRuleId}/put/summary Operation object should contain `summary` field. 337 | "deprecated": false 338 | }, 339 | "put": { | ^^^^^ 340 | "tags": [ 341 | "appTrafficRules" Error was generated by the operation-summary rule. [4] ../specs/MecAppSupportApi.json:494:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules/get/summary Operation object should contain `summary` field. 492 | }, 493 | "/applications/{appInstanceId}/dns_rules": { 494 | "get": { | ^^^^^ 495 | "tags": [ 496 | "appDnsRules" Error was generated by the operation-summary rule. [5] ../specs/MecAppSupportApi.json:624:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/get/summary Operation object should contain `summary` field. 622 | }, 623 | "/applications/{appInstanceId}/dns_rules/{dnsRuleId}": { 624 | "get": { | ^^^^^ 625 | "tags": [ 626 | "appDnsRules" Error was generated by the operation-summary rule. [6] ../specs/MecAppSupportApi.json:726:7 at #/paths/~1applications~1{appInstanceId}~1dns_rules~1{dnsRuleId}/put/summary Operation object should contain `summary` field. 724 | "deprecated": false 725 | }, 726 | "put": { | ^^^^^ 727 | "tags": [ 728 | "appDnsRules" Error was generated by the operation-summary rule. [7] ../specs/MecAppSupportApi.json:860:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object should contain `summary` field. 858 | }, 859 | "/applications/{appInstanceId}/subscriptions": { 860 | "get": { | ^^^^^ 861 | "tags": [ 862 | "appSubscriptions" Error was generated by the operation-summary rule. [8] ../specs/MecAppSupportApi.json:940:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object should contain `summary` field. 938 | "deprecated": false 939 | }, 940 | "post": { | ^^^^^^ 941 | "tags": [ 942 | "appSubscriptions" Error was generated by the operation-summary rule. [9] ../specs/MecAppSupportApi.json:1046:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/summary Operation object should contain `summary` field. 1044 | "AppTerminationNotification": { 1045 | "{$request.body#/callbackUri}": { 1046 | "post": { | ^^^^^^ 1047 | "description": "Represents the information that the MEP notifies the subscribed application instance about the corresponding applic...<21 chars> 1048 | "operationId": "AppTerminationNotification_POST", Error was generated by the operation-summary rule. [10] ../specs/MecAppSupportApi.json:1068:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object should contain `summary` field. 1066 | }, 1067 | "/applications/{appInstanceId}/subscriptions/{subscriptionId}": { 1068 | "get": { | ^^^^^ 1069 | "tags": [ 1070 | "appSubscriptions" Error was generated by the operation-summary rule. [11] ../specs/MecAppSupportApi.json:1158:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object should contain `summary` field. 1156 | "deprecated": false 1157 | }, 1158 | "delete": { | ^^^^^^^^ 1159 | "tags": [ 1160 | "appSubscriptions" Error was generated by the operation-summary rule. [12] ../specs/MecAppSupportApi.json:1227:7 at #/paths/~1applications~1{appInstanceId}~1confirm_termination/post/summary Operation object should contain `summary` field. 1225 | }, 1226 | "/applications/{appInstanceId}/confirm_termination": { 1227 | "post": { | ^^^^^^ 1228 | "tags": [ 1229 | "appConfirmTermination" Error was generated by the operation-summary rule. [13] ../specs/MecAppSupportApi.json:1351:7 at #/paths/~1applications~1{appInstanceId}~1confirm_ready/post/summary Operation object should contain `summary` field. 1349 | }, 1350 | "/applications/{appInstanceId}/confirm_ready": { 1351 | "post": { | ^^^^^^ 1352 | "tags": [ 1353 | "appConfirmReady" Error was generated by the operation-summary rule. [14] ../specs/MecAppSupportApi.json:1475:7 at #/paths/~1timing~1timing_caps/get/summary Operation object should contain `summary` field. 1473 | }, 1474 | "/timing/timing_caps": { 1475 | "get": { | ^^^^^ 1476 | "tags": [ 1477 | "timing" Error was generated by the operation-summary rule. [15] ../specs/MecAppSupportApi.json:1547:7 at #/paths/~1timing~1current_time/get/summary Operation object should contain `summary` field. 1545 | }, 1546 | "/timing/current_time": { 1547 | "get": { | ^^^^^ 1548 | "tags": [ 1549 | "timing" Error was generated by the operation-summary rule. [16] ../specs/MecAppSupportApi.json:20:5 at #/tags/0/description Tag object should contain `description` field. 18 | }, 19 | "tags": [ 20 | { | ^ 21 | "name": "appTrafficRules" | ^^^^^^^^^^^^^^^^^^^^^^^^^ 22 | }, | ^ 23 | { 24 | "name": "appDnsRules" Warning was generated by the tag-description rule. [17] ../specs/MecAppSupportApi.json:23:5 at #/tags/1/description Tag object should contain `description` field. 21 | "name": "appTrafficRules" 22 | }, 23 | { | ^ 24 | "name": "appDnsRules" | ^^^^^^^^^^^^^^^^^^^^^ 25 | }, | ^ 26 | { 27 | "name": "appSubscriptions" Warning was generated by the tag-description rule. [18] ../specs/MecAppSupportApi.json:26:5 at #/tags/2/description Tag object should contain `description` field. 24 | "name": "appDnsRules" 25 | }, 26 | { | ^ 27 | "name": "appSubscriptions" | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 28 | }, | ^ 29 | { 30 | "name": "appConfirmTermination" Warning was generated by the tag-description rule. [19] ../specs/MecAppSupportApi.json:29:5 at #/tags/3/description Tag object should contain `description` field. 27 | "name": "appSubscriptions" 28 | }, 29 | { | ^ 30 | "name": "appConfirmTermination" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 31 | }, | ^ 32 | { 33 | "name": "appConfirmReady" Warning was generated by the tag-description rule. [20] ../specs/MecAppSupportApi.json:32:5 at #/tags/4/description Tag object should contain `description` field. 30 | "name": "appConfirmTermination" 31 | }, 32 | { | ^ 33 | "name": "appConfirmReady" | ^^^^^^^^^^^^^^^^^^^^^^^^^ 34 | }, | ^ 35 | { 36 | "name": "timing" Warning was generated by the tag-description rule. [21] ../specs/MecAppSupportApi.json:35:5 at #/tags/5/description Tag object should contain `description` field. 33 | "name": "appConfirmReady" 34 | }, 35 | { | ^ 36 | "name": "timing" | ^^^^^^^^^^^^^^^^ 37 | }, | ^ 38 | { 39 | "name": "callbacks" Warning was generated by the tag-description rule. [22] ../specs/MecAppSupportApi.json:38:5 at #/tags/6/description Tag object should contain `description` field. 36 | "name": "timing" 37 | }, 38 | { | ^ 39 | "name": "callbacks" | ^^^^^^^^^^^^^^^^^^^ 40 | } | ^ 41 | ], 42 | "jsonSchemaDialect": "https://json-schema.org/draft/2020-12/schema", Warning was generated by the tag-description rule. [23] ../specs/MecAppSupportApi.json:1055:17 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/AppTerminationNotification/{$request.body#~1callbackUri}/post/responses Operation must have at least one `4xx` response. 1053 | "$ref": "#/components/requestBodies/AppTerminationNotification" 1054 | }, 1055 | "responses": { | ^^^^^^^^^^^ 1056 | "200": { 1057 | "description": "Expected responses from callback consumer, if it accepts the callback" Warning was generated by the operation-4xx-response rule. s/MecAppSupportApi.json: validated in 197ms ❌ Validation failed with 15 errors and 8 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.
---- Validating ./MecServiceMgmtApi.json: No configurations were defined in extends -- using built in recommended configuration by default. validating s/MecServiceMgmtApi.json... [1] ../specs/MecServiceMgmtApi.json:52:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/get/summary Operation object should contain `summary` field. 50 | "paths": { 51 | "/applications/{appInstanceId}/subscriptions": { 52 | "get": { | ^^^^^ 53 | "tags": [ 54 | "appSubscriptions" Error was generated by the operation-summary rule. [2] ../specs/MecServiceMgmtApi.json:132:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/summary Operation object should contain `summary` field. 130 | "deprecated": false 131 | }, 132 | "post": { | ^^^^^^ 133 | "tags": [ 134 | "appSubscriptions" Error was generated by the operation-summary rule. [3] ../specs/MecServiceMgmtApi.json:238:15 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/summary Operation object should contain `summary` field. 236 | "ServiceAvailailityNotification": { 237 | "{$request.body#/callbackReference}": { 238 | "post": { | ^^^^^^ 239 | "description": "'Represents the service availability information that is used in the following cases
 when the MEC platform anno...<416 chars> 240 | "operationId": "ServiceAvailabilityNotification_POST", Error was generated by the operation-summary rule. [4] ../specs/MecServiceMgmtApi.json:260:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/get/summary Operation object should contain `summary` field. 258 | }, 259 | "/applications/{appInstanceId}/subscriptions/{subscriptionId}": { 260 | "get": { | ^^^^^ 261 | "tags": [ 262 | "appSubscriptions" Error was generated by the operation-summary rule. [5] ../specs/MecServiceMgmtApi.json:350:7 at #/paths/~1applications~1{appInstanceId}~1subscriptions~1{subscriptionId}/delete/summary Operation object should contain `summary` field. 348 | "deprecated": false 349 | }, 350 | "delete": { | ^^^^^^^^ 351 | "tags": [ 352 | "appSubscriptions" Error was generated by the operation-summary rule. [6] ../specs/MecServiceMgmtApi.json:419:7 at #/paths/~1applications~1{appInstanceId}~1services/get/summary Operation object should contain `summary` field. 417 | }, 418 | "/applications/{appInstanceId}/services": { 419 | "get": { | ^^^^^ 420 | "tags": [ 421 | "appServices" Error was generated by the operation-summary rule. [7] ../specs/MecServiceMgmtApi.json:672:7 at #/paths/~1applications~1{appInstanceId}~1services/post/summary Operation object should contain `summary` field. 670 | "deprecated": false 671 | }, 672 | "post": { | ^^^^^^ 673 | "tags": [ 674 | "appServices" Error was generated by the operation-summary rule. [8] ../specs/MecServiceMgmtApi.json:826:7 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 824 | }, 825 | "/applications/{appInstanceId}/services/{serviceId}": { 826 | "get": { | ^^^^^ 827 | "tags": [ 828 | "appServices" Error was generated by the operation-summary rule. [9] ../specs/MecServiceMgmtApi.json:954:7 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/put/summary Operation object should contain `summary` field. 952 | "deprecated": false 953 | }, 954 | "put": { | ^^^^^ 955 | "tags": [ 956 | "appServices" Error was generated by the operation-summary rule. [10] ../specs/MecServiceMgmtApi.json:1111:7 at #/paths/~1applications~1{appInstanceId}~1services~1{serviceId}/delete/summary Operation object should contain `summary` field. 1109 | "deprecated": false 1110 | }, 1111 | "delete": { | ^^^^^^^^ 1112 | "tags": [ 1113 | "appServices" Error was generated by the operation-summary rule. [11] ../specs/MecServiceMgmtApi.json:1180:7 at #/paths/~1services/get/summary Operation object should contain `summary` field. 1178 | }, 1179 | "/services": { 1180 | "get": { | ^^^^^ 1181 | "tags": [ 1182 | "services" Error was generated by the operation-summary rule. [12] ../specs/MecServiceMgmtApi.json:1426:7 at #/paths/~1services~1{serviceId}/get/summary Operation object should contain `summary` field. 1424 | }, 1425 | "/services/{serviceId}": { 1426 | "get": { | ^^^^^ 1427 | "tags": [ 1428 | "services" Error was generated by the operation-summary rule. [13] ../specs/MecServiceMgmtApi.json:1547:7 at #/paths/~1transports/get/summary Operation object should contain `summary` field. 1545 | }, 1546 | "/transports": { 1547 | "get": { | ^^^^^ 1548 | "tags": [ 1549 | "transports" Error was generated by the operation-summary rule. [14] ../specs/MecServiceMgmtApi.json:1624:7 at #/paths/~1resource_uri_allocated_by_MEC_platform/get/summary Operation object should contain `summary` field. 1622 | }, 1623 | "/resource_uri_allocated_by_MEC_platform": { 1624 | "get": { | ^^^^^ 1625 | "tags": [ 1626 | "individualMECservice" Error was generated by the operation-summary rule. [15] ../specs/MecServiceMgmtApi.json:1673:7 at #/paths/~1resource_uri_allocated_by_MEC_platform/patch/summary Operation object should contain `summary` field. 1671 | } 1672 | }, 1673 | "patch": { | ^^^^^^^ 1674 | "tags": [ 1675 | "individualMECservice" Error was generated by the operation-summary rule. [16] ../specs/MecServiceMgmtApi.json:31:5 at #/tags/0/description Tag object should contain `description` field. 29 | ], 30 | "tags": [ 31 | { | ^ 32 | "name": "appSubscriptions" | ^^^^^^^^^^^^^^^^^^^^^^^^^^ 33 | }, | ^ 34 | { 35 | "name": "appServices" Warning was generated by the tag-description rule. [17] ../specs/MecServiceMgmtApi.json:34:5 at #/tags/1/description Tag object should contain `description` field. 32 | "name": "appSubscriptions" 33 | }, 34 | { | ^ 35 | "name": "appServices" | ^^^^^^^^^^^^^^^^^^^^^ 36 | }, | ^ 37 | { 38 | "name": "services" Warning was generated by the tag-description rule. [18] ../specs/MecServiceMgmtApi.json:37:5 at #/tags/2/description Tag object should contain `description` field. 35 | "name": "appServices" 36 | }, 37 | { | ^ 38 | "name": "services" | ^^^^^^^^^^^^^^^^^^ 39 | }, | ^ 40 | { 41 | "name": "transports" Warning was generated by the tag-description rule. [19] ../specs/MecServiceMgmtApi.json:40:5 at #/tags/3/description Tag object should contain `description` field. 38 | "name": "services" 39 | }, 40 | { | ^ 41 | "name": "transports" | ^^^^^^^^^^^^^^^^^^^^ 42 | }, | ^ 43 | { 44 | "name": "callbacks" Warning was generated by the tag-description rule. [20] ../specs/MecServiceMgmtApi.json:43:5 at #/tags/4/description Tag object should contain `description` field. 41 | "name": "transports" 42 | }, 43 | { | ^ 44 | "name": "callbacks" | ^^^^^^^^^^^^^^^^^^^ 45 | }, | ^ 46 | { 47 | "name": "individualMECservice" Warning was generated by the tag-description rule. [21] ../specs/MecServiceMgmtApi.json:46:5 at #/tags/5/description Tag object should contain `description` field. 44 | "name": "callbacks" 45 | }, 46 | { | ^ 47 | "name": "individualMECservice" | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 48 | } | ^ 49 | ], 50 | "paths": { Warning was generated by the tag-description rule. [22] ../specs/MecServiceMgmtApi.json:247:17 at #/paths/~1applications~1{appInstanceId}~1subscriptions/post/callbacks/ServiceAvailailityNotification/{$request.body#~1callbackReference}/post/responses Operation must have at least one `4xx` response. 245 | "$ref": "#/components/requestBodies/ServiceAvailabilityNotification" 246 | }, 247 | "responses": { | ^^^^^^^^^^^ 248 | "200": { 249 | "description": "Expected responses from callback consumer, if it accepts the callback" Warning was generated by the operation-4xx-response rule. s/MecServiceMgmtApi.json: validated in 194ms ❌ Validation failed with 15 errors and 7 warnings. run `openapi lint --generate-ignore-file` to add all problems to the ignore file.


------ Content of the folder ------
LICENSE
MecAppSupportApi.json
MecAppSupportApi.yaml
MecServiceMgmtApi.json
MecServiceMgmtApi.yaml
openapi-validation.log
README.md
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] updateGitlabCommitStatus
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // gitlabBuilds
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE