Standalone app deploy fails imsOrgId must be defined
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
### 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
Contributor guide
Research direction
Start by reviewing the GitHub workflow YAML configuration for the standalone, action-only app and trace the aio app deployment entry point. Reproduce the CI/CD deployment and determine what configuration is missing; done means the workflow deploys successfully without the "imsOrgId must be defined" error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100