Hello,
We are encountering an error after upgrading the aio-cli version from 10.3.4 to 11.0.0.
The current Node.js version is node-v20.18.0.
Error message:
› Error: [IMSSDK:CONTEXT_NOT_CONFIGURED] IMS context 'onboarding-config' is not configured
After reverting to aio-cli version 10.3.4, the aio commands (such as deploy) started working without any issues. We used the following command to revert:
npm install -g @adobe/aio-cli@10.3.4
Can someone please help us resolve the error encountered with @adobe/aio-cli/11.0.0?
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
I faced the same issue while upgrading the aio-cli from version 10.3.4 to 11.0.0
After the upgrade, whenever I try to deploy my actions using the aio app deploy am getting an error during deployment.
Error: Unknown Error From API: getaddrinfo ENOTFOUND deploy-service.app-builder.adp.adobe.io
Hi @rxraj, could you please help me resolve this issue or advise me on what might be causing the error after upgrading the CLI?
Currently, I revert to the previous version as you suggested, and it is working
Views
Replies
Total Likes
Please send output of
aio info
Views
Replies
Total Likes
Please send output of
aio info
Views
Replies
Total Likes
Please refer to the output of the aio info command.
System:
OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
Memory: 7.44 GB / 23.21 GB
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 20.18.0 - ~/.nvm/versions/node/v20.18.0/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 10.8.2 - ~/.nvm/versions/node/v20.18.0/bin/npm
Virtualization:
Docker: 24.0.2 - /usr/bin/docker
npmGlobalPackages:
@adobe/aio-cli: 11.0.0
Proxies:
http: (not set)
https: (not set)
CLI plugins:
core:
@adobe/aio-cli 11.0.0
@adobe/aio-cli-plugin-app 14.1.3
@adobe/aio-cli-plugin-app-dev 2.1.2
@adobe/aio-cli-plugin-app-storage 1.1.0
@adobe/aio-cli-plugin-app-templates 2.0.3
@adobe/aio-cli-plugin-auth 4.0.1
@adobe/aio-cli-plugin-certificate 2.0.1
@adobe/aio-cli-plugin-config 5.0.1
@adobe/aio-cli-plugin-console 5.0.1
@adobe/aio-cli-plugin-events 4.0.1
@adobe/aio-cli-plugin-info 4.0.1
@adobe/aio-cli-plugin-runtime 8.0.0
@adobe/aio-cli-plugin-telemetry 2.0.2
@oclif/plugin-autocomplete 3.2.34
@oclif/plugin-help 6.2.32
@oclif/plugin-not-found 2.4.3
@oclif/plugin-plugins 5.4.46
@oclif/plugin-warn-if-update-available 3.1.46
user:
@adobe/aio-cli-plugin-api-mesh 5.4.1
link:
I also tried renaming the ~/.config/aio file, but it did not work.
Views
Replies
Total Likes
@rxraj are you using the commerce starter kit by any chance?
Views
Replies
Total Likes
Yes, After upgrading the aio-cli to version 11.0.0, we encountered this error while deploying the application to the runtime.
Views
Replies
Total Likes
Please continue to use version 10.3.4 of the CLI while we open a bug with the commerce team to look into this.
This error has been reproduced in older versions of the commerce starter kit when clearing the context configuration. The CLI defaults to a context named 'onboarding-config' which doesn't exist in your current setup.
Recommended Solution: Update your code to the latest commerce starter kit version, as this issue has been resolved there. If you need a quick fix for your current setup, simply run
npm run onboard
This will automatically recreate the missing context and get your aio deploy commands working again with version 11.0.0. Alternatively, run
aio context --list
to see available contexts, then use
aio context -s <context-name>
to switch to an existing one.
Views
Replies
Total Likes
Views
Replies
Total Likes
Yes, developers can continue using CLI version 11 and beyond without any issues. We haven't encountered any problems using CLI version 11 with the latest commerce starter kit. If anyone experiences any errors with CLI version 11, please let us know what you were doing when the error occurred and confirm you're using the latest starter kit version and we'll investigate and help resolve any issues you encounter.
Thank you @martinpa
The application deployment with the aio-cli@11.0.0 is now functioning correctly for the commerce starter kit.
Previously, we encountered 'onboarding-config' context errors along with the "getaddrinfo ENOTFOUND deploy-service.app-builder.adp.adobe.io" error while using the commerce starter kit v3.0.0.
https://github.com/adobe/commerce-integration-starter-kit/releases/tag/v3.0.0
Views
Replies
Total Likes
Views
Like
Replies
Views
Likes
Replies