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
Follow the vendor generation steps at the root of this repository and generate a vendored folder (referenced in application.yaml).
I can see that vendor directory is created after build.sh example.jsonnet as docs/customizing.md describes.
Where is vendored directory? should I rename vendor to vendored?
Before that, how the k8s resource can reference the direcotry? e.g.
kubectl apply -n argocd application.yaml
Should I fork this repo to create a vendored directory and update the URL of the repo in the application.yaml?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
One of the requirements (at examples/continuous-delivery/argocd) is:
I can see that
vendor
directory is created afterbuild.sh example.jsonnet
as docs/customizing.md describes.Where is
vendored
directory? should I renamevendor
tovendored
?Before that, how the k8s resource can reference the direcotry? e.g.
Should I fork this repo to create a
vendored
directory and update the URL of the repo in theapplication.yaml
?Beta Was this translation helpful? Give feedback.
All reactions