You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I opctl run notAnOp and notAnOp is a valid directory but has no op.yml, I don't get a fancy error.
To Reproduce
Create a directory at ./.opspec/notAnOp
Run opctl run notAnOp
Expected behavior
fancy error:
unable to resolve op 'notAnOp':
- filesystem:
- path [omitted]/.opspec/notAnOp/op.yml not found
- path [omitted]/notAnOp/op.yml not found
- opctl node: unable to resolve op 'notAnOp':
- filesystem: skipped
- git: invalid git ref: missing version
Actual Behavior
open /Users/chrisdostert/repos/github.com/opctl/opctl/cli/.opspec/test/op.yml: no such file or directory
The text was updated successfully, but these errors were encountered:
@apexskier maybe you'd be interested/willing to take on
apexskier
changed the title
Fancy resolution error not working when valid dir but not valid op (no op.yml)
Op refs to directories missing an op.yml aren't caught as data resolution errors
Mar 31, 2021
馃悰 Bug Report
When I
opctl run notAnOp
andnotAnOp
is a valid directory but has noop.yml
, I don't get a fancy error.To Reproduce
./.opspec/notAnOp
opctl run notAnOp
Expected behavior
fancy error:
Actual Behavior
The text was updated successfully, but these errors were encountered: