Release v0.13.0

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2021-05-26 14:45:14 +03:00
parent 909d98b9bc
commit 145a82a429
No known key found for this signature in database
GPG Key ID: 3299AEB0E4085BAF
4 changed files with 35 additions and 14 deletions

View File

@ -2,6 +2,27 @@
All notable changes to this project are documented in this file.
## 0.13.0
**Release date:** 2021-05-26
This prerelease comes with support for including the contents of a Git repository into another.
The [include feature](https://github.com/fluxcd/source-controller/blob/api/v0.13.0/docs/spec/v1beta1/gitrepositories.md#including-gitrepository)
has multiple benefits over regular Git submodules:
* Including a `GitRepository` allows you to use different authentication methods for different repositories.
* A change in the included repository will trigger an update of the including repository.
* Multiple `GitRepositories` could include the same repository, which decreases the amount of cloning done compared to using submodules.
Features:
* Add include property to GitRepositories
[#348](https://github.com/fluxcd/source-controller/pull/348)
Improvements:
* Update Git packages
[#365](https://github.com/fluxcd/source-controller/pull/365)
## 0.12.2
**Release date:** 2021-05-10

View File

@ -6,4 +6,4 @@ resources:
images:
- name: fluxcd/source-controller
newName: fluxcd/source-controller
newTag: v0.12.2
newTag: v0.13.0

View File

@ -492,23 +492,23 @@ to a user that has access to the main repository and all its submodules.
### Including GitRepository
With `spec.include` you can map the contents of a git repository into another.
This may look identical to git submodules but has multiple benefits over
regular submodules.
With `spec.include` you can map the contents of a Git repository into another.
This may look identical to Git submodules but has multiple benefits over
regular submodules:
* Including a GitRepository allows you to use different authentication methods for different repositories.
* Including a `GitRepository` allows you to use different authentication methods for different repositories.
* A change in the included repository will trigger an update of the including repository.
* Multiple GitRepositories could include the same repository, which decreases the amount of cloning done compared to using submodules.
* Multiple `GitRepositories` could include the same repository, which decreases the amount of cloning done compared to using submodules.
```yaml
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
name: repo1
name: app-repo
namespace: default
spec:
interval: 1m
url: https://github.com/<organization>/repo1
url: https://github.com/<org>/app-repo
secretRef:
name: https-credentials
ref:
@ -517,20 +517,20 @@ spec:
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
name: repo2
name: config-repo
namespace: default
spec:
interval: 1m
url: https://github.com/<organization>/repo2
url: https://github.com/<org>/config-repo
secretRef:
name: https-credentials
ref:
branch: main
include:
- repository:
name: repo1
from: manifests
to: manifests
name: app-repo
from: deploy/kubernetes
to: base/app
---
apiVersion: v1
kind: Secret

2
go.mod
View File

@ -17,7 +17,7 @@ require (
github.com/fluxcd/pkg/ssh v0.0.5
github.com/fluxcd/pkg/untar v0.0.5
github.com/fluxcd/pkg/version v0.0.1
github.com/fluxcd/source-controller/api v0.12.2
github.com/fluxcd/source-controller/api v0.13.0
github.com/go-git/go-billy/v5 v5.3.1
github.com/go-git/go-git/v5 v5.4.1
github.com/go-logr/logr v0.4.0