Describe the bug
When an aliasified package is deployed to Prod, it fails if it does not contain a prod-specific folder. The Prod deployment does not use the default package.
To Reproduce
Steps to reproduce the behavior:
Create an aliasified package without a "prod" folder, but with a "default" folder
Attempt to deploy the aliasified package to a Production environment
Per the logs, the default folder is selected, but the deployment fails. The error message received is Error: Aliasfied package 'redhatcrm-loyalty-mgmt-env-specific' does not have an alias with 'prod' or 'default' directory, which is inaccurate, as this package does have a default directory, as shown in the screenshot below.
Describe the bug When an aliasified package is deployed to Prod, it fails if it does not contain a prod-specific folder. The Prod deployment does not use the default package.
To Reproduce Steps to reproduce the behavior:
Per the logs, the default folder is selected, but the deployment fails. The error message received is
Error: Aliasfied package 'redhatcrm-loyalty-mgmt-env-specific' does not have an alias with 'prod' or 'default' directory, which is inaccurate, as this package does have a default directory, as shown in the screenshot below.On reviewing the documentation, I can find no mention of this behavior, but it's clearly specified in the code (https://github.com/flxbl-io/sfp/blob/5082c8802c0e53f3075fedda610fec746440bd0d/src/core/package/packageInstallers/InstallPackage.ts#L145-L159).
Expected behavior
Screenshots
Platform Details (please complete the following information):