Skip to content
This repository was archived by the owner on Mar 18, 2024. It is now read-only.
This repository was archived by the owner on Mar 18, 2024. It is now read-only.

Ignore empty aliasfied package during the validation #1419

@ruslan-kurchenko

Description

@ruslan-kurchenko

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:
Screenshot 2023-10-05 at 13 20 55

folders structure:
Screenshot 2023-10-05 at 13 23 37
Screenshot 2023-10-05 at 13 24 06

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

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions