How to import a remote module (on Artifactory)

[nocquidant]

Hi, I am looking for help to use a remote module because I am constantly reusing the same files in my projects.

My remote module is simple and will be designed like this:

types.pkl # defines types for variables 
variables.pkl # import "./types.pkl" ie using a relative path 
module.pkl # Define the module name 

Using the remote module would be to amend the remote object vars (created in the remote module).

import "the remote module"
vars {
   // amends the vars object
}

I would like to host the module on our private Artifactory instance. Because it is simpler than our private Gitlab instance (no token/credentials needed).

I think I have 2 solutions

1. Use pkl http endpoints and target individual files: types.pkl and variables.pkl files. But I'm not sure that the relative import in variables.pkl would work... And also no caching here (not a big deal though).
2. Use the directive package to import my module. But does it work with an archive file deposited on an http server like Artifactory? I'm missing documentation here.

Thanks
--nick

[nocquidant]

OK I've just found the CLI to prepare a package..
So it should work on Artifactory.

[bioball]

Yup, the pkl project package command creates the assets that you need to upload to Artifactory.

Note that where you upload determines what your package name and what the packageZipUrl should be. See https://pkl-lang.org/main/current/language-reference/index.html#package-asset-uri for more details.