Looking at second generation packaging for managed packages and am a bit confused on feature parity with 1st gen with regards to managed packages..
Primary concern is that things are set up correctly or if we should just stay with 1st gen packaging.
The documentation is pretty sparse. Primary concerns are LMA support and multiple packages under the same namespace
One of the benefits of second gen packaging is having multiple packages under one namespace. However, in order to associate a namespace with a scratch org to develop the package the namespace have to be registered in the dev hub org.
Currently the only way I see to register a namespace is to create a developer edition org via the environment hub.
Easy enough, but then how would you create multiple packages under that namespace? The answer to this may depend on some of the answer to the following questions
If one has the developer edition org with namespace and the namespace is registered, how do you create the package using second generation packaging.
When using the packaging command you can generate a package with the namespace but then where does it live? I highly doubt the code will automagically be populated in the namespace org.
Given that there is no UI for second generation packaging, how would one support the package in subscriber orgs? Do you still get LMA records created for installations of managed second generation packages if there is no code in the namespace org?
Wrap up question
Is the developer org holding the namespace only there to provide the namespace? Does any code ever make it to the namespace org?
Keep in mind the goal is to have a solution with multiple packages under the same namespace..
Is second gen packaging not read for prime time with managed packages in this scenario and we should stick with 1st generation packaging.