Hannes Hörl

This is nothing that `counterfeiter` comes with OOTB, however you can implement it relatively easy yourself by providing a stub: ```go func TestSomething(t *testing.T) { fakeAdder := foooofakes.FakeAdder{} fakeAdder.AddCalls(func(a, b...

A different approach could be to introduce the notion of a header. By default it should be `// Code generated by counterfeiter. DO NOT EDIT.`. But users can override that....

Well, I don't REALLY need it -- I can always slap some sh around counterfeiter which handles that. However I believe that this usecase (having a licence header or such...

I do prefer committing generated code for the most part, because it allows users to clone the repo and just run the thing (where in case of counterfeiter "the thing"...

> Try putting the stemcell version in quotes in your config file. It appears the yank value is being read as a float instead of a string. RIght. That might...

I had the very same issue again with: - `om` from the platform automation `5.0.19` - Opsman `2.10.24-build.360` I have the suspicion, that if you once rolled out a newer...

... and forwarding rules for the policy API please.

That would help, but I think we'd need the same for the "outer directory": ```yaml apiVersion: vendir.k14s.io/v1alpha1 kind: Config directories: - path: vendir_vendor permission: 755 #!

> think it is useful to have permissions on both levels or only the main would be enough? I _think_ there might be cases where you want them do be...

> On your local machine you did a vendir sync and afterward, you decided to change permission on your file on disk. The next time you do a vendir sync...