Standalone app deploy fails imsOrgId must be defined

[hthakkar2905]

Expected Behaviour

App gets deployed with CI CD.

Actual Behaviour

Deployment fails with error "imsOrgId must be defined"

Reproduce Scenario (including but not limited to)

1. Create a standalone app using aio CLI that has action only

Steps to Reproduce

1. Create a standalone app with action only
2. Make sure github workflow yml is configured as per documentation
3. Deploy using github CI CD

Platform and Version

Sample Code that illustrates the problem

Attached screenshots of code structure and how deployment yml looks like.

Logs taken while reproducing problem

[aguacatedan]

I've been struggling with this issue the past few days as well and I went through the very painful process of reading the source code to understand what exactly I was missing.

In short, I solved this by setting my IMS Org ID in the CI/CD pipeline prior to the deploy command:
aio config:set -l project.org.ims_org_id foobar@AdobeOrg

This sets the ims_org_id in the project's local .aio config file. If you look at yours in your IDE, you'll see it's already set and that probably happened sometime during aio app init. So rather than adding this config file to source control, adding that config property through the CLI did it for me.

I did find some interesting comments in the cli source code hinting that this imsOrgId property will be going away sometime in the future, but I didn't find any information in the official docs:

• https://github.com/adobe/aio-cli-lib-app-config/blob/ca93bf4740342601bab1df3d1657a0b47855cadc/src/index.js#LL178C42-L178C42
• https://github.com/adobe/aio-lib-runtime/blob/4e27e3217e62ee401ca746d16a93e7e4e7c49684/src/utils.js#L1430

[hthakkar2905]

Hi @aguacatedan
Yeah setting up IMS org id in previous step fixed it. Thanks for your help.

I just added additional step before deploy like this

- name: Set IMS Org ID
        run: |
          aio config:set -l project.org.ims_org_id ${{ secrets.IMSORGID_STAGE }}

[MichaelGoberling]

@hthakkar2905 @aguacatedan

Is this issue still present with the latest version (3.3.0) if you remove the step to setup the IMS Org ID?