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

Aliasfied packages are ignored in Validate with Release Config #1289

Closed
petter-eikeland opened this issue Apr 18, 2023 · 0 comments · Fixed by #1293
Closed

Aliasfied packages are ignored in Validate with Release Config #1289

petter-eikeland opened this issue Apr 18, 2023 · 0 comments · Fixed by #1293
Assignees
@azlam-abdulsalam
Labels
breaking bug Something isn't working
Milestone
Release - April 2023

Comments

@petter-eikeland
Copy link

Describe the bug
Aliasfied packages are ignored in Validate with Release Config. Giving the "aliasfy": true in sfdx-project.json makes sfpowerscripts ignore that particular package during Validate

To Reproduce
Steps to reproduce the behavior:

  1. Use validate with release config (e.g. --mode=thorough-release-config)
  2. Add aliasfied package to release config

Expected behavior
Aliasfied packages are deployed during validate

Screenshots
image
image

Platform Details (please complete the following information):

  • OS: Linux
  • Version: Version:20.30.4 -Release:March 23
  • Salesforce CLI(sfdx cli) Version: 7.186.2
  • CI Platform: Azure DevOps

Additional context
Add any other context about the problem here.
@github-actions github-actions bot added the analysis To be decided on how to solution/fix label Apr 18, 2023
@azlam-abdulsalam azlam-abdulsalam mentioned this issue Apr 19, 2023
Merged
5 tasks
azlam-abdulsalam added a commit that referenced this issue Apr 19, 2023
@azlam-abdulsalam
fix(validate): aliasified packages are ignored in validate
e4c3611 
BREAKING CHANGE: validate command will now respect aliasified
[packages. This means aliasified packages which do not have
a default directory will fail during validation. To fix this,
either ignore the package or add a default directory to the
aliasified package which is the contents that you want
to deploy to the scratch origin

fixes #1289]
@azlam-abdulsalam azlam-abdulsalam linked a pull request Apr 19, 2023 that will close this issue
fix(validate): aliasified packages are ignored in validate #1293
Merged
5 tasks
@azlam-abdulsalam azlam-abdulsalam self-assigned this Apr 19, 2023
@azlam-abdulsalam azlam-abdulsalam added bug Something isn't working breaking and removed analysis To be decided on how to solution/fix labels Apr 19, 2023
azlam-abdulsalam added a commit that referenced this issue Apr 24, 2023
@azlam-abdulsalam
fix(validate): aliasified packages are ignored in validate (#1293)
3bcf94a 
BREAKING CHANGE: validate command will now respect aliasified
[packages. This means aliasified packages which do not have
a default directory will fail during validation. To fix this,
either ignore the package or add a default directory to the
aliasified package which is the contents that you want
to deploy to the scratch origin

fixes #1289]
@azlam-abdulsalam azlam-abdulsalam added this to the Release - April 2023 milestone Apr 25, 2023
@Schuchie Schuchie mentioned this issue Apr 2, 2024
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@azlam-abdulsalam azlam-abdulsalam

Labels
breaking bug Something isn't working
Projects
None yet
Milestone
Release - April 2023
Development

Successfully merging a pull request may close this issue.

fix(validate): aliasified packages are ignored in validate dxatscale/sfpowerscripts
2 participants
@azlam-abdulsalam @petter-eikeland