You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
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 #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 #1418 as it can impact this item too.
Slack Message
The text was updated successfully, but these errors were encountered: