Packaging rules typically emit two artifacts, one named after the rule's name and is overall easy to identify, and one that is templated with a bunch of other metadata, like timestamps, change numbers, and versions, and is not so easy to identify programatically.

PackageArtifactInfo helps alleviate this problem by giving users a provider interface for identifying the complex-named artifact. Accessing it, however, requires that users implement custom rule logic to access it.

One potential way for working around this is use output groups. These can emitted in the appropriate providers, and then specific artifacts can be consumed by specifying the output_group attribute of the filegroup rule, with no custom rule logic required.