Releases: kubernetes/git-sync
v4.3.0
What's Changed
- Add docs on symlink and "the contract" by @thockin in #916
- fix: recover when there is unreleased lock file by @sdowell in #914
- Add support for GitHub app authentication by @risset in #878
New Contributors
Full Changelog: v4.2.4...v4.3.0
Available at: registry.k8s.io/git-sync/git-sync:v4.3.0
Contributors
Assets 2
v4.2.4
What's Changed
- Support -? as an alias for --help by @thockin in #882
- Bump go to 1.22 by @thockin in #884
- Log cleanups by @thockin in #887
- Add curl to the image by @thockin in #888
- Clean up flag-related messages by @thockin in #883
- Add the idea of "env-flags" by @thockin in #886
New Contributors
- @rul made their first contribution in #892
- @VICIWUOHA made their first contribution in #904
Full Changelog: v4.2.3...v4.2.4
Available at: registry.k8s.io/git-sync/git-sync:v4.2.4
Contributors
Assets 2
v4.2.3
What's Changed
- Base-image CVEs are resolved.
Full Changelog: v4.2.2...v4.2.3
Available at: registry.k8s.io/git-sync/git-sync:v4.2.3
v4.2.2
What's Changed
- Use bash instead of dash by @thockin in #866
- fix(auth): Fix ssh authentication by @yyvess in #868
- Bump base bookworm image to 1.0.2 by @dims in #871
New Contributors
- @jmichalek132 made their first contribution in #862
- @yyvess made their first contribution in #868
- @dims made their first contribution in #871
- @demoth made their first contribution in #870
Full Changelog: v4.2.1...v4.2.2
Available at: registry.k8s.io/git-sync/git-sync:v4.2.2
Contributors
Assets 2
v4.2.1
What's Changed
- CVE fixes in base-image
Full Changelog: v4.2.0...v4.2.1
Available at: registry.k8s.io/git-sync/git-sync:v4.2.1
v4.2.0
Most important changes:
- Try not to log credentials
- Fix a bug with symlinks when --link is not under --root
- Change the inner loop to be even simpler
What's Changed
- Log less verbose flags in less verbose modes by @thockin in #837
- Update the v3-to-v4 doc to cover some changes that I missed by @thockin in #843
- Bug: links are relative to linkdir, not rootdir by @thockin in #848
- Simplify inner loop: just fetch $ref by @thockin in #845
- Bump actions/setup-go from 4 to 5 by @dependabot in #850
- Try not to log credentials in repo URL by @thockin in #852
- Bump to go 1.21 by @thockin in #858
- Add '-F none' to e2e git SSH command for weird environments by @thockin in #859
Full Changelog: v4.1.0...v4.2.0
Available at: registry.k8s.io/git-sync/git-sync:v4.2.0
Contributors
Assets 2
v4.1.0
This is minor overall, but includes a couple flag changes which warranted bumping the minor version.
--sshis no longer needed (but still accepted)--credentialis new, to enable submodules with different usernames/passwords- Multiple SSH key are supported, to enable submodules with different keys
- Better logging (minor)
- Fix some corner cases for failure modes
Available at: registry.k8s.io/git-sync/git-sync:v4.1.0
What's Changed
- fix: Fix backward compatibility of environment variables with bool type by @phil-park in #798
- Add $GITSYNC_VERBOSE to set verbosity via env by @thockin in #805
- Support multiple SSH keys for use in submodules by @thockin in #802
- Print correct key on env-parse errors by @thockin in #812
- Set core.askPass config for better auth-fail error by @thockin in #815
- Deprecate --ssh - it's not really needed by @thockin in #822
- Document V4 regression on --change-permissions by @thockin in #809
- Add --credential flag for multiple username/password by @thockin in #803
- Fix errors when parsing --repo for logging by @thockin in #830
- fix: infinite bad loop caused by unexpected worktree directory removal by @bakome in #828
- Logging: log syncCount and be less scary by @thockin in #835
- Recover if wrong worktree HEAD by @thockin in #836
New Contributors
- @phil-park made their first contribution in #798
- @dependabot made their first contribution in #800
- @bakome made their first contribution in #828
Full Changelog: v4.0.0...v4.1.0
Contributors
Assets 2
v4.0.0
This is the first GA release of git-sync v4.
Available at: registry.k8s.io/git-sync/git-sync:v4.0.0
Git-sync v4 is a significant change from v3. It includes several flag changes
(though many of the old flags are kept for backwards compatibility), but more
importantly it fundamentally changes the way the internal sync-loop works.
It should be possible to upgrade a synced repo (e.g. in a volume) from git-sync
v3 to git-sync v4, but appropriate caution should be used for critical
deployments. We have a test which covers this, but there are many degrees of
config which we simply can't predict.
The v3 loop
The way git-sync v3.x works is sort of like how a human might work:
git clone <repo> <branch>git fetch <remote>git checkout <ref>
This made the code somewhat complicated, since it had to keep track of whether
this was the first pass (clone) or a subsequent pass (fetch). This led to a
number of bugs related to back-to-back runs of git-sync, and some race
conditions.
The v4 loop
In v4.x the loop is simpler - every pass is the same. This takes advantage of
some idempotent behaviors (e.g. git init is safe to re-run) and uses git more
efficiently. Instead of cloning a branch, git-sync will now fetch exactly the
commit (by SHA) it needs. This transfers less data and closes the race
condition where a symbolic name can change after git ls-remote but before
git fetch.
Flags
The flag syntax parsing has changed in v4. git-sync v3 accept flags in Go's
own style: either -flag or --flag were accepted. git-sync v4 only accepts
long flag names in the more common two-dash style (--flag), and accepts short
(single-character) flags in the one-dash style (-v 2).
The following does not detail every flag available in v4 - just the one that
existed in v3 and are different in v4.
Verbosity: --v -> -v or --verbose
The change in flag parsing affects the old --v syntax. To set verbosity
either use -v or --verbose. For backwards compatibility, --v will be
used if it is specified.
Sync target: --branch and --rev -> --ref
The old --branch and --rev flags are deprecated in favor of the new --ref
flag. --ref can be either a branch name, a tag name, or a commit hash (aka
SHA). For backwards compatibility, git-sync will still accept the old flags
and try to set --ref from them.
|----------|---------|---------|------------------------------|
| --branch | --rev | --ref | meaning |
|----------|---------|---------|------------------------------|
| "" | "" | "HEAD" | remote repo's default branch |
| brname | "" | brname | remote branch `brname` |
| brname | "HEAD" | brname | remote branch `brname` |
| "" | tagname | tagname | remote tag `tagname` |
| other | other | "" | error |
|----------|---------|---------|------------------------------|
Log-related flags
git-sync v3 exposed a number of log-related flags (e.g. -logtostderr). These
have all been removed. git-sync v4 always logs to stderr, and the only control
offered is the verbosity level (-v / --verbose).
Symlink: --dest -> --link
The old --dest flag is deprecated in favor of --link, which more clearly
conveys what it does. The allowed values remain the same, and for backwards
compatibility, --dest will be used if it is specified.
Loop: --wait -> --period
The old --wait flag took a floating-point number of seconds as an argument
(e.g. "0.1" = 100ms). The new --period flag takes a Go-style duration string
(e.g. "100ms" or "0.1s" = 100ms). For backwards compatibility, --wait will
be used if it is specified.
Failures: --max-sync-failures -> --max-failures
The new name of this flag is shorter and captures the idea that any
non-recoverable error in the sync loop counts as a failure. For backwards
compatibility, --max-sync-failures will be used if it is specified.
Timeouts: --timeout -> --sync-timeout
The old --timeout flag took an integer number of seconds as an argument. The
new --sync-timeout flag takes a Go-style duration string (e.g. "30s" or
"0.5m"). For backwards compatibility, --timeout will be used if it is
specified.
Permissions: --change-permissions -> --group-write
The old --change-permissions flag was poorly designed and not able to express
the real intentions (e.g. "allow group write" does not mean "set everything to
0775"). The new --group-write flag should cover what people ACTUALLY are
trying to do. The --change-permissions flag is no longer supported.
Manual: --man
The new --man flag prints a man-page style help document and exits.
Env vars
Most flags can also be configured by environment variables. In v3 the
variables all start with GIT_SYNC_. In v4 they all start with GITSYNC_,
though the old names are still accepted for compatibility.
Defaults
Depth
git-sync v3 would sync the entire history of the remote repo by default. v4
syncs just one commit, by default. This can be a significant performance and
disk-space savings for large repos. Users who want the full history can
specify --depth=0.
Logs
The logging output for v3 was semi-free-form text. Log output in v4 is
structured and rendered as strict JSON.
Root dir
git-sync v3 container images defaulted --root to "/tmp/git". In v4, that has
moved to "/git". Users who mount a volume and expect to use the default
--root must mount it on "/git".
Hooks
git-sync v3 could "lose" exechook and webhook calls in the face of the app
restarting. In v4, app startup is treated as a sync, even if the correct hash
was already present, which means that hooks are always called.
Other changes
git-sync v3 would allow invalidly formatted env vars (e.g. a value that was
expected to be boolean holding an integer) and just ignore them with
a warning. v4 requires that they parse correctly.
What's Changed since v4.0.0-rc5
Nothing!
Notable changes
- Add help and manual flags, use pflag by @thockin in #298
- Change time-related flags to durations by @thockin in #299
- Add tests for other env funcs by @thockin in #301
- Change some flags (breaking) by @thockin in #300
- Add a test for tabs in manual by @thockin in #305
- Normalize the root path by @thockin in #302
- Clarify logging vs printf for fatal messages by @thockin in #303
- Add a "main struct" with methods by @thockin in #304
- Add the
--rootflag into the Usage section by @haiyanmeng in #307 - Change CONTRIBUTING.md to CNCF CLA by @thockin in #318
- Allow octal and hex values for int flags by @thockin in #322
- Log info about UID, GID, and HOME for debug by @thockin in #323
- Add an example pod YAML by @thockin in #328
- Default the git-sync root dir in container by @thockin in #330
- Use docker to run helper servers in e2e by @thockin in #332
- Makefile: Update base and build images by @justaugustus in #336
- Update git from backports by @thockin in #347
- Build container without cache by @thockin in #349
- Change the symlink targets to just the SHA (v4) by @thockin in #351
- Fix tests on master - reset needs "--" arg by @thockin in #353
- Add --git-config flag by @thockin in #342
- Fix exit non-zero exit codes when running as pid1 by @thockin in #344
- Don't require a TTY to build/test by @thockin in #362
- Copy all licenses into the container image (v4) by @thockin in #366
- Move sync-hook to after symlink flip by @thockin in #370
- Update to latest base image debian-base:buster-v1.6.0 (v4) by @thockin in #377
- Fix licenses for other arch'es by @thockin in #379
- Export the error details to an error file by @nan-yu in #375
- Sort the flags in the manual output by @thockin in #380
- Add support for sparse-checkout (v4 vbranch) by @thockin in #381
- Create the root directory if it doesn't exist by @nan-yu in #385
- Clean up global flRoot use (v4) by @thockin in #386
- move test cleanup to the end (v4) by @thockin in #391
- Grant read access for the error file to all users by @nan-yu in #390
- Small error string cleanup (v4) by @thockin in #394
- Make sure all code files have headers by @thockin in https://github...
Contributors
Assets 2
v4.0.0-rc5
Compared to RC4 this includes:
- Fix permissions on /tmp in the container image
Converting from git-sync v3.x to v4.x
Git-sync v4 is a significant change from v3. It includes several flag changes
(though many of the old flags are kept for backwards compatibility), but more
importantly it fundamentally changes the way the internal sync-loop works.
It should be possible to upgrade a synced repo (e.g. in a volume) from git-sync
v3 to git-sync v4, but appropriate caution should be used for critical
deployments. We have a test which covers this, but there are many degrees of
config which we simply can't predict.
The v3 loop
The way git-sync v3.x works is sort of like how a human might work:
git clone <repo> <branch>git fetch <remote>git checkout <ref>
This made the code somewhat complicated, since it had to keep track of whether
this was the first pass (clone) or a subsequent pass (fetch). This led to a
number of bugs related to back-to-back runs of git-sync, and some race
conditions.
The v4 loop
In v4.x the loop is simpler - every pass is the same. This takes advantage of
some idempotent behaviors (e.g. git init is safe to re-run) and uses git more
efficiently. Instead of cloning a branch, git-sync will now fetch exactly the
commit (by SHA) it needs. This transfers less data and closes the race
condition where a symbolic name can change after git ls-remote but before
git fetch.
Flags
The flag syntax parsing has changed in v4. git-sync v3 accept flags in Go's
own style: either -flag or --flag were accepted. git-sync v4 only accepts
long flag names in the more common two-dash style (--flag), and accepts short
(single-character) flags in the one-dash style (-v 2).
The following does not detail every flag available in v4 - just the one that
existed in v3 and are different in v4.
Verbosity: --v -> -v or --verbose
The change in flag parsing affects the old --v syntax. To set verbosity
either use -v or --verbose. For backwards compatibility, --v will be
used if it is specified.
Sync target: --branch and --rev -> --ref
The old --branch and --rev flags are deprecated in favor of the new --ref
flag. --ref can be either a branch name, a tag name, or a commit hash (aka
SHA). For backwards compatibility, git-sync will still accept the old flags
and try to set --ref from them.
|----------|---------|---------|------------------------------|
| --branch | --rev | --ref | meaning |
|----------|---------|---------|------------------------------|
| "" | "" | "HEAD" | remote repo's default branch |
| brname | "" | brname | remote branch `brname` |
| brname | "HEAD" | brname | remote branch `brname` |
| "" | tagname | tagname | remote tag `tagname` |
| other | other | "" | error |
|----------|---------|---------|------------------------------|
Log-related flags
git-sync v3 exposed a number of log-related flags (e.g. -logtostderr). These
have all been removed. git-sync v4 always logs to stderr, and the only control
offered is the verbosity level (-v / --verbose).
Symlink: --dest -> --link
The old --dest flag is deprecated in favor of --link, which more clearly
conveys what it does. The allowed values remain the same, and for backwards
compatibility, --dest will be used if it is specified.
Loop: --wait -> --period
The old --wait flag took a floating-point number of seconds as an argument
(e.g. "0.1" = 100ms). The new --period flag takes a Go-style duration string
(e.g. "100ms" or "0.1s" = 100ms). For backwards compatibility, --wait will
be used if it is specified.
Failures: --max-sync-failures -> --max-failures
The new name of this flag is shorter and captures the idea that any
non-recoverable error in the sync loop counts as a failure. For backwards
compatibility, --max-sync-failures will be used if it is specified.
Timeouts: --timeout -> --sync-timeout
The old --timeout flag took an integer number of seconds as an argument. The
new --sync-timeout flag takes a Go-style duration string (e.g. "30s" or
"0.5m"). For backwards compatibility, --timeout will be used if it is
specified.
Permissions: --change-permissions -> --group-write
The old --change-permissions flag was poorly designed and not able to express
the real intentions (e.g. "allow group write" does not mean "set everything to
0775"). The new --group-write flag should cover what people ACTUALLY are
trying to do. The --change-permissions flag is no longer supported.
Manual: --man
The new --man flag prints a man-page style help document and exits.
Env vars
Most flags can also be configured by environment variables. In v3 the
variables all start with GIT_SYNC_. In v4 they all start with GITSYNC_,
though the old names are still accepted for compatibility.
Defaults
Depth
git-sync v3 would sync the entire history of the remote repo by default. v4
syncs just one commit, by default. This can be a significant performance and
disk-space savings for large repos. Users who want the full history can
specify --depth=0.
Logs
The logging output for v3 was semi-free-form text. Log output in v4 is
structured and rendered as strict JSON.
Root dir
git-sync v3 container images defaulted --root to "/tmp/git". In v4, that has
moved to "/git". Users who mount a volume and expect to use the default
--root must mount it on "/git".
Hooks
git-sync v3 could "lose" exechook and webhook calls in the face of the app
restarting. In v4, app startup is treated as a sync, even if the correct hash
was already present, which means that hooks are always called.
Other changes
git-sync v3 would allow invalidly formatted env vars (e.g. a value that was
expected to be boolean holding an integer) and just ignore them with
a warning. v4 requires that they parse correctly.
Available at: registry.k8s.io/git-sync/git-sync:v4.0.0-rc5
What's Changed since rc4
Full Changelog: v4.0.0-rc4...v4.0.0-rc5
Contributors
Assets 2
v4.0.0-rc4
Compared to RC3 this includes:
- OCI image now correctly reports debian 12
- Lint fixes
- Fix a leaked goroutine when parsing git options
- When credential refresh errors occur (e.g. askpass) we no longer try to sync
Converting from git-sync v3.x to v4.x
Git-sync v4 is a significant change from v3. It includes several flag changes
(though many of the old flags are kept for backwards compatibility), but more
importantly it fundamentally changes the way the internal sync-loop works.
It should be possible to upgrade a synced repo (e.g. in a volume) from git-sync
v3 to git-sync v4, but appropriate caution should be used for critical
deployments. We have a test which covers this, but there are many degrees of
config which we simply can't predict.
The v3 loop
The way git-sync v3.x works is sort of like how a human might work:
git clone <repo> <branch>git fetch <remote>git checkout <ref>
This made the code somewhat complicated, since it had to keep track of whether
this was the first pass (clone) or a subsequent pass (fetch). This led to a
number of bugs related to back-to-back runs of git-sync, and some race
conditions.
The v4 loop
In v4.x the loop is simpler - every pass is the same. This takes advantage of
some idempotent behaviors (e.g. git init is safe to re-run) and uses git more
efficiently. Instead of cloning a branch, git-sync will now fetch exactly the
commit (by SHA) it needs. This transfers less data and closes the race
condition where a symbolic name can change after git ls-remote but before
git fetch.
Flags
The flag syntax parsing has changed in v4. git-sync v3 accept flags in Go's
own style: either -flag or --flag were accepted. git-sync v4 only accepts
long flag names in the more common two-dash style (--flag), and accepts short
(single-character) flags in the one-dash style (-v 2).
The following does not detail every flag available in v4 - just the one that
existed in v3 and are different in v4.
Verbosity: --v -> -v or --verbose
The change in flag parsing affects the old --v syntax. To set verbosity
either use -v or --verbose. For backwards compatibility, --v will be
used if it is specified.
Sync target: --branch and --rev -> --ref
The old --branch and --rev flags are deprecated in favor of the new --ref
flag. --ref can be either a branch name, a tag name, or a commit hash (aka
SHA). For backwards compatibility, git-sync will still accept the old flags
and try to set --ref from them.
|----------|---------|---------|------------------------------|
| --branch | --rev | --ref | meaning |
|----------|---------|---------|------------------------------|
| "" | "" | "HEAD" | remote repo's default branch |
| brname | "" | brname | remote branch `brname` |
| brname | "HEAD" | brname | remote branch `brname` |
| "" | tagname | tagname | remote tag `tagname` |
| other | other | "" | error |
|----------|---------|---------|------------------------------|
Log-related flags
git-sync v3 exposed a number of log-related flags (e.g. -logtostderr). These
have all been removed. git-sync v4 always logs to stderr, and the only control
offered is the verbosity level (-v / --verbose).
Symlink: --dest -> --link
The old --dest flag is deprecated in favor of --link, which more clearly
conveys what it does. The allowed values remain the same, and for backwards
compatibility, --dest will be used if it is specified.
Loop: --wait -> --period
The old --wait flag took a floating-point number of seconds as an argument
(e.g. "0.1" = 100ms). The new --period flag takes a Go-style duration string
(e.g. "100ms" or "0.1s" = 100ms). For backwards compatibility, --wait will
be used if it is specified.
Failures: --max-sync-failures -> --max-failures
The new name of this flag is shorter and captures the idea that any
non-recoverable error in the sync loop counts as a failure. For backwards
compatibility, --max-sync-failures will be used if it is specified.
Timeouts: --timeout -> --sync-timeout
The old --timeout flag took an integer number of seconds as an argument. The
new --sync-timeout flag takes a Go-style duration string (e.g. "30s" or
"0.5m"). For backwards compatibility, --timeout will be used if it is
specified.
Permissions: --change-permissions -> --group-write
The old --change-permissions flag was poorly designed and not able to express
the real intentions (e.g. "allow group write" does not mean "set everything to
0775"). The new --group-write flag should cover what people ACTUALLY are
trying to do. The --change-permissions flag is no longer supported.
Manual: --man
The new --man flag prints a man-page style help document and exits.
Env vars
Most flags can also be configured by environment variables. In v3 the
variables all start with GIT_SYNC_. In v4 they all start with GITSYNC_,
though the old names are still accepted for compatibility.
Defaults
Depth
git-sync v3 would sync the entire history of the remote repo by default. v4
syncs just one commit, by default. This can be a significant performance and
disk-space savings for large repos. Users who want the full history can
specify --depth=0.
Logs
The logging output for v3 was semi-free-form text. Log output in v4 is
structured and rendered as strict JSON.
Root dir
git-sync v3 container images defaulted --root to "/tmp/git". In v4, that has
moved to "/git". Users who mount a volume and expect to use the default
--root must mount it on "/git".
Hooks
git-sync v3 could "lose" exechook and webhook calls in the face of the app
restarting. In v4, app startup is treated as a sync, even if the correct hash
was already present, which means that hooks are always called.
Other changes
git-sync v3 would allow invalidly formatted env vars (e.g. a value that was
expected to be boolean holding an integer) and just ignore them with
a warning. v4 requires that they parse correctly.
Available at: registry.k8s.io/git-sync/git-sync:v4.0.0-rc4
What's Changed since rc3
- Update README.md by @thockin in #771
- Update README.md by @Gemesil in #772
- Handle errors from credential refresh by @thockin in #778
- Drop distroless and DIY by @thockin in #781
- Remove trailing newlines from errors by @justinsb in #784
- Lint fixes (part 1) by @justinsb in #783
- Enable github actions for CI by @justinsb in #786
- Add dependabot for github actions by @thockin in #790
- Replace all error %v with %w by @thockin in #789
- Rename github build workflow by @thockin in #791
- Fix goroutine leak in git option parsing by @thockin in #788
- lint: fix remaining lint issues. by @justinsb in #792
- Add linters to makefile/github actions by @justinsb in #787
New Contributors
Full Changelog: v4.0.0-rc3...v4.0.0-rc4