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
The directory in the git repo that gets synced to /git in consul depends on what environment git2consul and consul are in. So if we're in the production uw1 AZ, then production_uw1 will get synced to /git in consul. This pattern has held up well so far, although we've recently been needing to introduce some data that would be shared across all environments.
We we're hoping this would work. It didn't. Admittedly this is kind of gross.
Version: 0.12.11
Error:
{"name":"git2consul","hostname":"ops.stg1.goldstarbeta.com","pid":27121,"level":50,"msg":"Failed to create repos due to Failed to load repo git due to Some consul updates failed:\nFailed to read key /var/lib/git2consul/cache/git/test-symlink/staging_stg1/global due to Error: EISDIR: illegal operation on a directory, read","time":"2016-10-13T19:58:39.759Z","v":0}
edit: I wanted to add that we worked around the issue, although I would still expect it to support symlinks, if at all possible. New configuration:
Our current git2consul repo has the following structure:
Our
repos
section of our git2consul config looks like this:The directory in the git repo that gets synced to
/git
in consul depends on what environment git2consul and consul are in. So if we're in the production uw1 AZ, thenproduction_uw1
will get synced to/git
in consul. This pattern has held up well so far, although we've recently been needing to introduce some data that would be shared across all environments.We tried to add in a symlink like so:
We we're hoping this would work. It didn't. Admittedly this is kind of gross.
Version: 0.12.11
Error:
edit: I wanted to add that we worked around the issue, although I would still expect it to support symlinks, if at all possible. New configuration:
The text was updated successfully, but these errors were encountered: