Replies: 2 comments
-
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@mshanemc Issue created as requested |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
tl;dr - Package2 and CLI have some unfortunate behaviors.
Just off long call with Support. Learned a few things:
Package2
has undocumented fields.IsDeprecated
andIsDeleted
(and others)sf package delete
does not delete the package. It marks it as deprecated.Deprecated packages can be renamed (BAD)
Expected Behaviors:
undeprecate
packages so we can, for example, rename themSteps To Reproduce
Create a
package
(2GP)Wait a minute or two
Query
SELECT Id, Name, NamespacePrefix, IsDeleted, IsDeprecated, SubscriberPackageID FROM Package2
until it actually shows upCreate a package version (may be unnecessary, but that's what we did)
Delete the package version
Delete the package with sf package delete
Run the query again
Expected result
The package you just made should not be there IF it is actually deleted.
Actual result
The package shows up and IsDeleted = false and IsDeprecated = true
System Information
OSX VSCode
Fresh org with fresh namespace registry org
Additional information
Beta Was this translation helpful? Give feedback.
All reactions