Install Nebula Logger via installedPackage-meta.xml

[brmsantos]

Hi!

I was wondering If it would be possible to install Nebula Logger by creating a new installedPackage-meta.xml file (in this case, Nebula.installedPackage-meta.xml). My reasoning:

• We use scratch orgs for development
• By adding the meta-xml specified above, I would be able to automatically and easily install the package both in new scratch orgs that have all of our metadata, or in sandboxes and Production, that are updated when new changes are merged into specific branches.
• Finally, by adding the metadata file, I would not need to change my pipeline logic in any way, as it would be just one more file in the codebase. If I can't do that, then I would need to add the sf install command to the pipeline (which, I know, is a small change).

After a few different attempts, I could not achieve that. The error message I get is: version number XYZ does not exist!.

In an ideal world, I would like to be able to install a managed package, because I would not like to run Nebula Logger-related tests in our pipeline, since we have many tests, and they take a while. At the same time, I would like to be able to expand the solution and send email notifications to specific users when a new error log is created. As far as I could tell, this is only possible with the unlocked package.

If I am missing something, please let me know. I was not able to find anything when researching in old discussions.

[jongpie]

@brmsantos the *.installedPackage-meta.xml files only work for first-generation packages (1GP) - both of Nebula Logger's packages (unlocked & managed) are 2GP, so you'll have to use the sf package install command.

As far as sending email alerts, there's not currently anything built for that (though it's in the backlog/something I'd like to eventually have built in). But in the meantime, the easiest option would be to build a record-triggered Flow in your org for the Log__c or LogEntry__c objects that sends an email.