Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Reference variables/envs/keys from other packages #1618

Open
artsiommiksiuk opened this issue Aug 20, 2024 · 0 comments
Open

[feature] Reference variables/envs/keys from other packages #1618

artsiommiksiuk opened this issue Aug 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@artsiommiksiuk
Copy link

Is your feature request related to a problem? Please describe.

E.g. I have a package A and package B. B depends on A to be build. I'd like to reference some files/outputs from A in B, so I don't have to copy/paste same strings in B.

This concept is close by it's utility as Bazel does it's artifacts referencing, where you can reference anything anywhere, given that the proper path in Bazel space specified.

Describe the solution you'd like

The way I see this is to have something like openAPI allows referencing

# a's moon.yaml

env:
  OUTPUT_DIR: "out/dir"
# b's moon.yaml
task:
  script: "echo @in(0)"
  inputs:
    - $ref: "A:envs.OUTPUT_DIR"

Describe alternatives you've considered

  1. Wait for .PKL migration?
  2. Copy/pasting same output path

Additional context

Basically I have a package which produces some artifact as a set of files. This files needs later to be used in another project in the same monorepo, for that I need to know the path where to copy them from.

@artsiommiksiuk artsiommiksiuk added the enhancement New feature or request label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant