-
Notifications
You must be signed in to change notification settings - Fork 78
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrieve package information #12
Comments
Please assume that I have a "sfdx-project.json" file and it has a valid ID I would like to execute the following command and receive back details about it. Command: Expected return: |
@sfdc-db-gmail please take a look |
@jefersonchaves - Can |
Hi @sfdc-db-gmail: it would work if I could retrieve information about Classic Managed Packages. My use case is: I want to retrieve information from Classic Managed Packages to use in a build, for instance. Makes sense? |
Hi @sfdc-db-gmail or @clairebianchi: is there anything else that I can assist? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Is your feature request related to a problem? Please describe.
Today there is no simple way to retrieve package information through Salesforce CLI. There is a need to parse
sfdx-project.json
and then use two Tooling API calls to retrieve package and package version information for a given alias.What are you trying to do
A description of the outcome you are hoping to achieve
Retrieve package information to display in build log and to retrieve the installation key from a secret text in Jenkins. This is also useful for local development.
Describe the solution you'd like
Would like to have another command in
force:package
that could retrieve package information. Could be something lkeforce:package:version:info
.Describe alternatives you've considered
Currently, I have implemented this as a Groovy script for Jenkins but I'm also considering writing a plugin.
The text was updated successfully, but these errors were encountered: