Rest API failure with HTTP(S) status 404

Products

• Brightside
• Endevor

Issue/Introduction

Tested "@broadcom/endevor-for-zowe-cli" with zowe v2(7.2.2) with Endevor V18.0.
And, when executed the "zowe endevor list elements" command, the following 404 error occurred.
No error occurred with zowe v1.

C:\Users\user-id>zowe endevor list elements
[INFO] Running on host: nn.nnn.nn.nnn:nnnnn instance: ENDEVOR
[INFO] LIST ELEMENTS executed in location: environment/n/system/subsystem on element: *.*
Command Error:
Rest API failure with HTTP(S) status 404
Error Details:
HTTP(S) error status "404" received.
Review request details (resource, base path, credentials, payload) and ensure correctness.

Protocol:  http
Host:      nn.nnn.nn.nnn
Port:      nnnnn
Base Path: EndevorService/api/v2
Resource:  ENDEVOR/env/environment/stgnum/n/sys/system/subsys/subsystem/type/*/ele/*?data=all
Request:   GET
Headers:   [{"Accept":"application/json"},{"accept-encoding":"gzip,deflate"}]
Payload:   undefined

It seems that the profile settings have changed to config settings from V2.
Used the "zowe config convert-profiles --delete" command to convert to the config file.
Are some settings insufficient?

 

Environment

zowe v2(7.2.2)
Endevor V18.0

Cause

Endevor V18.0 does not support REST API V2, it possibly does not even support the REST API V1.

 

Resolution

Need to update the basePath of the team config(zowe.config.json) file.

From:
 "basePath": "EndevorService/api/v2",

To:
 "basePath": "EndevorService/rest",