-
-
Notifications
You must be signed in to change notification settings - Fork 867
Closed
Description
Bug Report
I have two custom resources. The first one is only used with put
to trigger deployments. With a put
I am passing it files from other resources, which it then proceeds to read and process:
- name: deploy-staging
plan:
- get: repo
passed: [build]
- put: custom-deployment-resource
params:
version: repo/.git/HEAD
This works fine. However, I'm not having any luck doing the same on get
:
- name: deploy
plan:
- get: repo
passed: [build]
- get: generate-config
params:
version: repo/.git/HEAD
This resolves in "No such file or directory repo/.git/HEAD". Is this a feature, or am I doing something wrong?
Metadata
Metadata
Assignees
Labels
No labels