breaking changes after "upgrade" - problems with "run --local"? | Adobe Higher Education
Skip to main content
Urs_Boller
Community Advisor
Urs_BollerCommunity Advisor
Community Advisor
September 23, 2020
Beantwortet

breaking changes after "upgrade" - problems with "run --local"?

  • September 23, 2020
  • 1 Antwort
  • 1752 Ansichten

I just realized a strange behaviour - let's assume the problem is sitting in front of the desktop ...

nevertheless, maybe someone else has the same issue. What happened? I just upgraded npm packages and aio to latest versions and tried the "aio app run --local" as usual. What I see looks as if there is some deployment similar to "aio app deploy" for some of the files, especially the "manifest.yml". not only takes it a lot longer to build my local files, it also looks quite different than before. did something change in the build process?

But the most confusing part: I had an app up and running in the same environment (I used "aio app deploy" before) with a schedule to run every hour. after the uprade the hourly scheduled stopped working ... I checked the "aio runtime activation list" without seeing any error. I assume that the last "aio app run -- local" uploaded the manifest.yml and stopped the trigger ...

happy to provide more information and get response if somebody has similar issues...

Dieses Thema wurde für Antworten geschlossen.
Beste Antwort von sarahxxu

Hi @urs_boller 

Could you provide a bit more information to help us debug? How can we try to reproduce this?

 

Sarah

1 Antwort

sarahxxu
Adobe Employee
sarahxxuAdobe EmployeeAntwort
Adobe Employee
September 24, 2020

Hi @urs_boller 

Could you provide a bit more information to help us debug? How can we try to reproduce this?

 

Sarah

Urs_Boller
Community Advisor
Urs_BollerCommunity AdvisorAutor
Community Advisor
September 24, 2020

@sarahxxu 

here are the updates I made on npm packages:

"aio version" => "@adobe/aio-cli/3.7.0 win32-x64 node-v12.16.2"

 

I made another test and I think this is how you can deproduce the problem:

1) create an app with a trigger, eg. "alarms/interval" set to 5 min

2) run "aio app deploy" and check with "aio rt trigger list" that the trigger has been set

3) remove the trigger from "manifest.yml" (since it does not work on local dev)

4) run "aio app run --local" and check again the "aio rt trigger list" => the trigger on runtime has been removed

 

tell me what you need and I'll send you screenshots.... if you habe any commands that provide useful information, let me know

Allgemeine NutzungsbedingungenAccessibility statement

Loading footer...