The dependency aws-sdk was updated from 2.589.0 to 2.590.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The dependency webpack was updated from 4.41.2 to 4.41.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

test.

The dependency aws-sdk was updated from 2.603.0 to 2.604.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Remote storage uploadFile should not have a dependency towards appConfig https://github.com/adobe/aio-lib-web/blob/master/lib/remote-storage.js#L110

As we do for config.s3.folder we should pass specific values and not have remote storage depend on the config object https://github.com/adobe/aio-lib-web/blob/master/src/deploy-web.js#L45

parcel-bundler v1.x is now deprecated, and showing this message:

DEPRECATED ⚠️  - Parcel v1 is no longer maintained. Please migrate to v2, which is published
under the 'parcel' package. See https://v2.parceljs.org/getting-started/migration for details.

We need to verify that everything still functions as expected, since this is a major bump.
Also, of note, parcel still lists 'latest' as a beta version => 2.0.0-beta.2

The dependency @adobe/aio-lib-core-config was updated from 1.0.15 to 1.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/aio-lib-core-config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency aws-sdk was updated from 2.594.0 to 2.595.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Release ow jar in this repo https://github.com/chetanmeh/incubator-openwhisk/releases/download/v0.10/openwhisk-standalone.jar to get a better url

This might be an issue since for the CLI, only node 8 is required.
See: https://github.com/adobe/adobeio-cna-scripts/blob/78ac7b9f43592061e7ab9adb94c04bcf857c8a24/package.json#L13

Expected Behaviour

When called at the root of a CNA project folder, aio cna undeploy should remove all the actions and package used by this CNA.

Actual Behaviour

If the application is run and debugged remotely (aio cna run + CNA debugging with wskdebug profile), some proxy actions are created within the application package.
These actions are not stored in the manifest.yml and therefore not handled by https://github.com/adobe/adobeio-cna-scripts/blob/master/scripts/undeploy.actions.js

This results in an error like on the screenshot below:

Reproduce Scenario (including but not limited to)

Please look at the steps below:

• CNA creation
• CNA add another action (e.g. 'goodbye')
• CNA remote debugging of the 'hello' action
• CNA deploy
• CNA undeploy

Steps to Reproduce

$ aio cna init helloworld //just use the wizard default values
$ cp _your_dot_env helloworld/
$ cd helloworld

// add a second action in the actions folder and declare it in the manifest.yml
// for example 'goodbye', with a simple index.js implementation

$ aio cna run

// just set a breakpoint in the hello index.js file and launch a debugging session...
// Quit the debugging session and go back to your term

$ aio cna deploy
$ aio cna undeploy

// Error happens, the goodbye_wskdebug_original action is not undeployed

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Please see the screenshot

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency webpack was updated from 4.42.1 to 4.43.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Do you provide support for Linux?

In the following setup:

• Fresh Debian 10 installed
• AIO-CLT installed
• Docker installed
• App generated with a "generic" action.

there is an issue:

The application is not available when trying to start using aio app run --local
A timeout is given.

I tried the following:

Docker's network interface is docker0 with IP 172.17.0.1

3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:99:4a:ab:f8 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

I changed this file manually:

/home/marko/.nvm/versions/node/v12.14.1/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-app-scripts/scripts/dev.js

const OW_LOCAL_APIHOST = 'http://172.17.0.1:3233'

This is working now.

I also tried to put

AIO_RUNTIME_APIHOST=http://172.17.0.1:3233

to .env before starting using aio app run --local. But this didn't work

Expected Behaviour

An end-user should always access the latest deployment of a Project Firefly SPA from the browser.
This means that the browser should load the latest version of the static files from the cache.

The TTLs are defined as follow:

• 1 min for HTML
• 7 days for every other mime type

The Parcel bundler generates content hashes for the static files, which are used as selectors to ensure the expected behavior.

Actual Behaviour

The Parcel bundler doesn't generate new hashes upon static files updates, which forces the end-user to manually clean the browser cache in order to use the latest SPA deployment.

Reproduce Scenario (including but not limited to)

• Create a new SPA using the aio CLI
• Deploy the SPA using aio app deploy
• Access the deployed SPA from your browser
• Update the SPA front-end code (e.g. update some JS or CSS file)
• Redeploy the SPA using aio app deploy
• Even after one minute delay and page refresh, the deployed changes are not loaded in the browser
• Manually clean the cache of your browser or access the deployed SPA from another browser
• The deployed changes are loaded in the browser

The dependency aws-sdk was updated from 2.627.0 to 2.628.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

• Better dev command instructions
• remove todos for dev command

In my node verision (v12.13.0), when the constructor for Boolean (at the line [1]) gets a string "false" as an input, the return is a boolean with a value true. It deals with any non-empty string as a true value.

One possible solution is to replace this line with (similar to [2]):
config.actions.devRemote = Boolean(process.env.REMOTE_ACTIONS === "true")

[1] https://github.com/adobe/aio-app-scripts/blob/3c6fc2bbfe6f53092fce55f9787513d4de803fb6/lib/config-loader.js#L111
[2] https://stackoverflow.com/a/264037

expectAppFiles has deep expectations of what the root file system looks like.
The tests should not actually touch the file system at all.

  ● with local actions and no frontend › should cleanup generated files on SIGINT

    expect(received).toEqual(expected) // deep equality

    - Expected
    + Received

      Set {
        "actions",
        "manifest.yml",
        "package.json",
    +   "repos",
        "web-src",
      }

      163 |   if (files.has('Users')) files.delete('Users')
      164 |   if (files.has('home')) files.delete('home')
    > 165 |   expect(files).toEqual(expectedFiles)
          |                 ^
      166 | }

This helps reduce the size.

See adobe/aio-cli#349
See https://www.npmjs.com/package/@aws-sdk/client-s3

Expected Behaviour

Create an app, run the app with "--local", add a breakpoint in run the action and run the debugger. When action is executed, the debugger pause the execution.

Actual Behaviour

The debugger does not start.

Steps to Reproduce

On a fresh new app, run aio app run --local.
Open VC Code and hit the Run Action:<app>-0.0.1/<action> button from the debugger.

The debugger starts but crashes immediately:

Error: Action not found: <app>-0.0.1/<action>
    at AgentMgr.peekAction (/Users/acapt/work/dev/helix/playground/test/node_modules/@openwhisk/wskdebug/src/agentmgr.js:104:19)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Environment Info

  System:
    OS: macOS 10.15.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 2.60 GB / 32.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.21.0 - ~/.nvm/versions/node/v10.21.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v10.21.0/bin/npm
  Virtualization:
    Docker: 19.03.12 - /usr/local/bin/docker
  npmGlobalPackages:
    @adobe/aio-cli: 3.7.0

Workaround

I found the issue: the .env file contains the runtime_auth and runtime_namespace twice (almost lower case and uppercase) and the debugger use the lowercase one while it should use the uppercase one.
In fact, the "local override" does not work anymore because of the letters case.

AIO_runtime_auth=abc
AIO_runtime_namespace=def
SERVICE_API_KEY=
AIO_LAUNCH_URL_PREFIX=https://experience.adobe.com/?devMode=true#/custom-apps/?localDevUrl=
AIO_RUNTIME_APIHOST=http://localhost:3233
AIO_RUNTIME_AUTH=xyz
AIO_RUNTIME_NAMESPACE=guest

Workaround is to stop the server, edit the .env and uppercase the 2 variables: AIO_RUNTIME_AUTH and AIO_RUNTIME_NAMESPACE.

cc @meryllblanchet

Expected Behaviour

àio app run|deploy|...should work even if there are hidden files in theactions` folder.

Actual Behaviour

When there is any hidden file in the actions folder, building actions will fail.
aio will complain about the hidden file not being a folder.
This happens a lot on mac os if the OS creates hidden .DS_Store files (e.g. if you sort your icons by name).

Reproduce Scenario (including but not limited to)

Add a hidden file in the actions folder and try to build an aio app.

Steps to Reproduce

• Create a hiden file starting with a dot ..
• Put this file into the actions folder.
• Try to build the aio-app.

Platform and Version

MAC OS X, latest aio.

Sample Code that illustrates the problem

N/A

Logs taken while reproducing problem

N/A

The dependency @adobe/aio-lib-core-config was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/aio-lib-core-config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

If there are no actions in the repo the runDev script fails

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency aws-sdk was updated from 2.652.0 to 2.653.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

See: https://github.com/adobe/adobeio-cna-scripts/blob/8edb2ddc27d5a58c6f2dcf2b7cff9a3def46fadc/lib/config-loader.js#L117

Sample manifest:

packages:
  __APP_PACKAGE__:
    license: Apache-2.0
    actions:
      report:
        function: /Users/himar/hello.js
        runtime: 'nodejs:10'
    triggers:
      everyMinute:
        feed: /whisk.system/alarms/alarm
        inputs:
          cron: "* * * * *"
          trigger_payload: "{\"message\": \"hello world!\"}"
    rules:
      reportEveryMinute:
        action: report
        trigger: everyMinute

It seems rules cannot be annotated and hence they cannot be fetched to undeploy.
Rules should be fetched the same way APIs are fetched from the manifest.

Expected Behaviour

rules should be undeployed

Actual Behaviour

rules are not undeployed

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

See adobe/aio-lib-files#107

The dependency open was updated from 7.0.0 to 7.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

open is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency @adobe/aio-cli-plugin-runtime was updated from 1.4.0 to 1.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/aio-cli-plugin-runtime is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

See #158

Expected Behaviour

All subdirectories under my /dist/web-src-prod should be uploaded to CDN.

Actual Behaviour

Only files under /dist/web-src-prod are uploaded.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

My build process generates a /dist/web-src-prod directory that looks like this:

.
├── index.html
├── resources // <=== THIS does not get uploaded
│   ├── README.MD
│   ├── spectrum-css-icons.svg
│   ├── spectrum-icons-color.svg
│   └── spectrum-icons.svg
├── src.a2b27638.css
├── src.a2b27638.css.map
├── src.a2b27638.js
├── src.a2b27638.js.map

When I run aio app deploy -v

I get this in the logs:

> Deploy static files
⚠ an already existing deployment for version 0.0.3 will be overwritten
   > static.txt
   > index.html
   > src.a2b27638.css
   > src.a2b27638.css.map
   > src.a2b27638.js
   > src.a2b27638.js.map
✔ Deploy static files

I have traced this issue to here:
https://github.com/adobe/aio-app-scripts/blob/e588449852e0afa53a57dbed290f39f2495d76ca/lib/remote-storage.js#L107

fs-extra does not support recursively walking the filesystem tree, The fs-extra author recommends using klaw here: https://github.com/jprichardson/node-fs-extra#what-happened-to-walk-and-walksync
or you could you any number of implementations to get the same result of including the whole directory recursively.

It's missing my resources folder

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

React Spectrum is the default UI toolkit for Project Firefly.
React Spectrum is written in TypeScript.
Unfortunately, Project Firefly does not support writing React + TypeScript thus we can't leverage all the benefits of React Spectrum.

Parcel is used to bundle static files https://github.com/adobe/aio-app-scripts/blob/master/scripts/build.ui.js#L47. but it's not configurable currently.

See https://en.parceljs.org/typeScript.html#when-using-react for more information about Parcel + React + TypeScript.

The function downloadOWJar is called with no logger so when this line [1] tries to log something, it fails

[1] https://github.com/adobe/aio-app-scripts/blob/3c6fc2bbfe6f53092fce55f9787513d4de803fb6/lib/utils.js#L185

This is the place that this function is called from:
https://github.com/adobe/aio-app-scripts/blob/3c6fc2bbfe6f53092fce55f9787513d4de803fb6/scripts/dev.js#L64

The devDependency @types/hapi__joi was updated from 16.0.8 to 16.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/hapi__joi is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency aws-sdk was updated from 2.614.0 to 2.615.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @types/jest was updated from 24.0.24 to 24.0.25.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/hapi__joi was updated from 16.0.6 to 16.0.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/hapi__joi is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Expected Behaviour

The code references a tokens action. See https://github.com/adobe/adobeio-cna-lib-auth-ims/blob/master/src/providers/IMSAuthCode.js#L51 .

Actual Behaviour

Should it be included ?

Describe the bug
A static project containing .mst files (mustache templates) can not be deployed. Debug log:

Deploying actions
⠋ Deploying web assets  @adobe/aio-lib-core-tvm:debug initializing with config: {
  @adobe/aio-lib-core-tvm:debug   "ow": {
  @adobe/aio-lib-core-tvm:debug     "namespace": "278519-mhtest-stage",
  @adobe/aio-lib-core-tvm:debug     "auth": "<hidden>"
  @adobe/aio-lib-core-tvm:debug   },
  @adobe/aio-lib-core-tvm:debug   "apiUrl": "https://firefly-tvm.adobe.io",
  @adobe/aio-lib-core-tvm:debug   "cacheFile": "/Users/mhaack/workspaces/playground/aio-pwa/.aws.tmp.creds.json"
  @adobe/aio-lib-core-tvm:debug }
  @adobe/aio-lib-core-tvm:debug read credentials from cache file with key b96338bb5bc5e6512bd5f8cf241b7168c3d302052818878a5188b8797fc8ef5c
TypeError: mimeType.startsWith is not a function
    at RemoteStorage._getCacheControlConfig (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-lib-web/lib/remote-storage.js:179:25)
    at RemoteStorage.uploadFile (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-lib-web/lib/remote-storage.js:110:37)
    at async /Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-lib-web/lib/remote-storage.js:157:21
    at async Promise.all (index 42)
    at async Object.deployWeb (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-lib-web/src/deploy-web.js:58:3)
    at async Deploy.run (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-app/src/commands/app/deploy.js:108:35)
    at async Deploy._run (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/command/lib/command.js:43:20)
    at async Config.runCommand (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/config/lib/config.js:173:24)
    at async Main.run (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/command/lib/main.js:27:9)
    at async Main._run (/Users/mhaack/.nvm/versions/node/v12.13.0/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/command/lib/command.js:43:20)

Sample files can be found here: https://github.com/magento/pwa-studio/tree/develop/packages/venia-ui/templates

Expected behavior
Deployment is working.

Additional context
aio cli version:

System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 441.09 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
    Yarn: 1.22.0 - /usr/local/bin/yarn
    npm: 6.12.0 - ~/.nvm/versions/node/v12.13.0/bin/npm
  Virtualization:
    Docker: 19.03.13 - /usr/local/bin/docker
  npmGlobalPackages:
    @adobe/aio-cli: 5.0.1
  CLI plugins:
    @adobe/aio-cli 5.0.1 (core)
    @adobe/aio-cli-plugin-app 5.2.1 (core)
    @adobe/aio-cli-plugin-auth 2.4.0 (core)
    @adobe/aio-cli-plugin-certificate 0.2.0 (core)
    @adobe/aio-cli-plugin-cloudmanager 0.18.2 (user)
    @adobe/aio-cli-plugin-config 2.3.0 (core)
    @adobe/aio-cli-plugin-console 3.2.0 (core)
    @adobe/aio-cli-plugin-events 1.1.0 (core)
    @adobe/aio-cli-plugin-info 1.1.1 (core)
    @adobe/aio-cli-plugin-runtime 3.0.0 (core)
    @oclif/plugin-autocomplete 0.2.0 (core)
    @oclif/plugin-help 2.2.3 (core)
    @oclif/plugin-not-found 1.2.4 (core)
    @oclif/plugin-plugins 1.9.4 (core)
    @oclif/plugin-warn-if-update-available 1.7.0 (core)

Not entirely sure if this should be done here, or in the cdn ...
user reported error:

https://some-app.adobeio-static.net/asset-manifest.json -> Failed to load resource: Origin http://localhost:4502 is not allowed by Access-Control-Allow-Origin

The dependency aws-sdk was updated from 2.608.0 to 2.609.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency aws-sdk was updated from 2.634.0 to 2.635.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Expected Behaviour

Add e2e tests for aio-lib-web
Related to: adobe/aio-e2e-tests#18

deploy fails if name in package.json contains a scope (starting with @)

Expected Behaviour

deploy should succeed

Actual Behaviour

deploy fails

Reproduce Scenario (including but not limited to)

deploy a package with a scope

Steps to Reproduce

deploy a package with a scope

Platform and Version

current (master)