Query with install_key in promote_package_version (via @zenibako) #3654
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r unlocked packages
Co-authored-by: David Reed <[email protected]>
jofsky
previously approved these changes
Sep 20, 2023
jofsky
approved these changes
Sep 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Via #3567)
If you attempt to use an installation key with the create_package_version and promote_package_version tasks (particularly with the build_unlocked_test_package flow), you will be blocked by a Salesforce SOQL error that demands you include the Installation key in the where clause of the query.
This PR updates these tasks and enables the build_unlocked_test_package flow to work when an installation key is configured for its tasks. It also adds install_key to promote_package_version as an option.