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

Zarf errors when absolute file paths are used in components.files.source #3475

Closed
AustinAbro321 opened this issue Feb 6, 2025 · 0 comments · Fixed by #3518
Closed

Zarf errors when absolute file paths are used in components.files.source #3475

AustinAbro321 opened this issue Feb 6, 2025 · 0 comments · Fixed by #3518

Comments

@AustinAbro321
Copy link
Contributor

Environment

App version: v0.47.0-v0.48.1

Steps to reproduce

  1. a zarf.yaml with a component with an absolute path
components:
  - name: baseline
    files:
      - source: /home/austin/code/zarf/cosign.pub
        target: here.pub
  1. build package with zarf package create

Expected result

The package builds successfully

Actual Result

2025-02-06 14:22:07 ERR failed to create package: unable to copy file /home/austin/code/secondZarf/cosign.pub: lstat home/austin/code/secondZarf/cosign.pub: no such file or directory

Severity/Priority

Medium, it seems this was already broken with imports, but allowed in the base package. It's simple enough to fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant