garden: Unable to overlap .gitignore setting
Bug
I can not manually include garden.yaml, when the project has own .git.
simplified folders structure
├── core
│ ├── .git
│ ├── garden.yml
└── garden.yml
where core is excluded from git.
# .gitignore
/core
# core/garden.yaml
---
# some config here
# ./garden.yaml
kind: Project
name: rp
modules:
include:
- core/garden.yaml
...
If try the same config with out .git folder in the projects- garden scan founds the configuration file.
Current Behavior
garden scan
✔ providers → Getting status... → Done
modules: []
Additional context
I tried to put it in another folder, which is not in .gitignore and with out own git repo, but it produced:
$ garden scan
Error validating module poker-core (support/core/garden.yml): key .dockerfile must be a relative sub-path (may not contain '..' segments or be an absolute path)
# support/core/garden.yaml
---
kind: Module
description: Image for poker-core
type: container
name: poker-core
dockerfile: ../../core/docker/development/Dockerfile
For me it is a blocker now.
Your environment
garden version
0.10.9
kubectl version
1.15.2
docker version
2.1.0.2
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15
Commits related to this issue
- fix(vcs): recursively handle submodules when scanning for files This is implemented by explicitly checking for configured submodules, and recursively scanning each submodule that passes the given ign... — committed to garden-io/garden by edvald 5 years ago
- fix(vcs): recursively handle submodules when scanning for files This is implemented by explicitly checking for configured submodules, and recursively scanning each submodule that passes the given ign... — committed to garden-io/garden by edvald 5 years ago
- fix(vcs): recursively handle submodules when scanning for files This is implemented by explicitly checking for configured submodules, and recursively scanning each submodule that passes the given ign... — committed to garden-io/garden by edvald 5 years ago
- fix(vcs): recursively handle submodules when scanning for files This is implemented by explicitly checking for configured submodules, and recursively scanning each submodule that passes the given ign... — committed to garden-io/garden by edvald 5 years ago
Understood. We’ll fix #1205 for sure, I figure that’ll be a blocker either way. But the shallow Git clone only applies if you don’t use
garden link. When you link a source, you attach directly to the local clone you have of the source repo, so you should see changes sync the same as with any other directory.