PM EMULATOR ERROR Code: config.compiler.InvalidEnvironment: Environment not found: 400

Google Cloud Apigee
,
1

YermekDevOps_0-1634895408277.png
YermekDevOps_0-1634895408277.png1812×1049 98.8 KB

Hi, dear Community,

Did anyone experience such issues already with Apigee Emulator?
What I’m possibly doing wrong?
My issue: Deploy fail to the Apigee Emulator. As on the screenshot, folder path exists. With the below message.
Steps to reproduce:

  • “Create Apigee workspace” from the “Cloud Code Apigee” plugin in VS Code.

  • Create proxy from the “Cloud Code Apigee” plugin in VS Code.

  • Start Apigee Emulator 1.6.1.

  • Deploy fails.

    Windows 10, VS Code 1.61.2, Cloud Code v1.16.0-insiders.3, gcr.io/apigee-release/hybrid/apigee-emulator 1.6.1.
    regards, Yermek

10/22/2021 2:30 PM EMULATOR INFO Deploying environment env-emu-sample, to Container wonderful_dewdney (Apigee runtime 1.6.1)
10/22/2021 2:30 PM EMULATOR ERROR Code   : config.compiler.InvalidEnvironment
10/22/2021 2:30 PM EMULATOR ERROR Message: Environment not found, it must be a folder named /src/main/apigee/environments/env-emu-sample/, and must have read permissions.
10/22/2021 2:30 PM EMULATOR ERROR File   : d:\projects\GitHub\workspace-emu-sample\src\main\apigee\environments\env-emu-sample:0:0
10/22/2021 2:30 PM EMULATOR ERROR Environment env-emu-sample deployment, to Container wonderful_dewdney (Apigee runtime 1.6.1) failed with Error: 400
10/22/2021 2:30 PM EMULATOR ERROR Deploy to Container wonderful_dewdney (Apigee runtime 1.6.1), failed with Error: Environment env-emu-sample deployment, to Container wonderful_dewdney (Apigee runtime 1.6.1) failed with Error: 400
2

Is possible for you to provide the output for

'unzip -l d:\projects\GitHub\workspace-emu-sample\target\emulator\deploy.zip"?

3

Hi, @shirishtrivikr

$ unzip -l deploy.zip
Archive:  deploy.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
      211  2021-10-22 09:30   apiproxies\proxy-sample\apiproxy\proxies\default.xml
      131  2021-10-22 09:30   apiproxies\proxy-sample\apiproxy\targets\default.xml
      186  2021-10-22 09:30   environments\env-emu-sample\debugmask.json
       81  2021-10-22 09:30   environments\env-emu-sample\deployments.json
        2  2021-10-22 09:30   environments\env-emu-sample\flowhooks.json
      129  2021-10-22 09:30   environments\env-emu-sample\targetservers.json
       97  2021-10-22 09:30   sharedflows\sf-sample\sharedflowbundle\sharedflows\default.xml
---------                     -------
      837                     7 files
4

@optimism Thanks for a quick reply. We are working on addressing this failure

5

Hi, @shirishtrivikr

how is it going, could you suggest, please?

regards, thanks

6

Could please update to insider build v1.16.0-insiders.4. We have included a fix for this issue.

7

@optimism was curious to know whether you were unblocked after upgrading to v1.16.0-insiders.4?