-
Notifications
You must be signed in to change notification settings - Fork 72
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #145 from fluxcd/release-v0.8.0
Release v0.8.0
- Loading branch information
Showing
6 changed files
with
70 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,15 +18,18 @@ type ImageUpdateAutomationSpec struct { | |
| // ready to make changes. | ||
| // +required | ||
| Checkout GitCheckoutSpec `json:"checkout"` | ||
|
|
||
| // Interval gives an lower bound for how often the automation | ||
| // run should be attempted. | ||
| // +required | ||
| Interval metav1.Duration `json:"interval"` | ||
|
|
||
| // Update gives the specification for how to update the files in | ||
| // the repository. This can be left empty, to use the default | ||
| // value. | ||
| // +kubebuilder:default={"strategy":"Setters"} | ||
| Update *UpdateStrategy `json:"update,omitempty"` | ||
|
|
||
| // Commit specifies how to commit to the git repository. | ||
| // +required | ||
| Commit CommitSpec `json:"commit"` | ||
|
|
@@ -132,13 +135,19 @@ type CommitSpec struct { | |
| // AuthorName gives the name to provide when making a commit | ||
| // +required | ||
| AuthorName string `json:"authorName"` | ||
|
|
||
| // AuthorEmail gives the email to provide when making a commit | ||
| // +required | ||
| AuthorEmail string `json:"authorEmail"` | ||
|
|
||
| // MessageTemplate provides a template for the commit message, | ||
| // into which will be interpolated the details of the change made. | ||
| // +optional | ||
| MessageTemplate string `json:"messageTemplate,omitempty"` | ||
|
|
||
| // SigningKey provides the option to sign commits with a GPG key | ||
| // +optional | ||
| SigningKey *SigningKey `json:"signingKey,omitempty"` | ||
| } | ||
| ``` | ||
|
|
||
|
|
@@ -167,6 +176,23 @@ spec: | |
| [ci skip] | ||
| ``` | ||
|
|
||
| The `signingKey` field holds the reference to a secret that contains a `git.asc` | ||
| key corresponding to the ASCII Armored file containing the GPG signing keypair as the value. | ||
| For example, | ||
|
|
||
| ```yaml | ||
| spec: | ||
| commit: | ||
| authorName: Fluxbot | ||
| authorEmail: [email protected] | ||
| signingKey: | ||
| secretRef: | ||
| name: gpg-private-key | ||
| ``` | ||
|
|
||
| will result in commits with the author `Fluxbot <[email protected]>` signed with the GPG key | ||
| present in the `gpg-private-key` secret. | ||
|
|
||
| ### Commit template data | ||
|
|
||
| The message template is a [Go text template][go-text-template]. The data available to the template | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters