During fast-feedback validation we are getting the issue: Aliasfied package 'env-meta-vars' does not have an alias with 'default' or 'default' directory
It is an MR validation job. We alias our CI org as "default" and there is a folder inside "env-meta-vars" with "default" folder
error log:
folders structure:
Issue Details:
dev, prod, staging and uat was changed but not default. In fast-feedback mode, it deploys only a delta. But there are no changes to the "default" folder and it causes issues because nothing is there.
Workaround:
Introduce dummy change to "default" folder too.
Proposed Solution:
The validation process should ignore aliasfied package if the deployment package is not found or empty. But we need to think about upcoming enhancement in the context of https://github.com/dxatscale/sfpowerscripts/pull/1418 as it can impact this item too.
During fast-feedback validation we are getting the issue: Aliasfied package 'env-meta-vars' does not have an alias with 'default' or 'default' directory
It is an MR validation job. We alias our CI org as "default" and there is a folder inside "env-meta-vars" with "default" folder
error log:
folders structure:
Issue Details: dev, prod, staging and uat was changed but not default. In fast-feedback mode, it deploys only a delta. But there are no changes to the "default" folder and it causes issues because nothing is there.
Workaround: Introduce dummy change to "default" folder too.
Proposed Solution: The validation process should ignore aliasfied package if the deployment package is not found or empty. But we need to think about upcoming enhancement in the context of https://github.com/dxatscale/sfpowerscripts/pull/1418 as it can impact this item too.
Slack Message