Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: bump the function image version to 0.13 in README.md #49

Merged
merged 1 commit into from
Jun 30, 2024
Merged

chore: bump the function image version to 0.13 in README.md #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,7 @@ metadata:
name: update-ksops-secrets
pipeline:
mutators:
- image: ghcr.io/neutronth/kpt-update-ksops-secrets:0.12
- image: ghcr.io/neutronth/kpt-update-ksops-secrets:0.13
configPath: update-ksops-secrets.yaml
```

Expand All @@ -173,7 +173,7 @@ Alternatively, invoke function directly without the `Kptfile`

```shell
$ kpt fn eval \
--image=ghcr.io/neutronth/kpt-update-ksops-secrets:0.12 \
--image=ghcr.io/neutronth/kpt-update-ksops-secrets:0.13 \
--fn-config=update-ksops-secrets.yaml
```

Expand Down Expand Up @@ -257,7 +257,7 @@ Hence, if the encrypted files recipients include the PGP/GPG fingerprints, the `

```shell
$ kpt fn eval \
--image=ghcr.io/neutronth/kpt-update-ksops-secrets:0.12 \
--image=ghcr.io/neutronth/kpt-update-ksops-secrets:0.13 \
--fn-config=update-ksops-secrets.yaml \
--network
```
Expand All @@ -269,6 +269,6 @@ The update-ksops-secrets supports in version described below:
- linux/amd64: >= 0.1
- linux/arm64: >= 0.12

### Operation mode encrypt once support
### Operation mode encrypt once support (>= 0.13)

The update-ksops-secrets supports the operation mode `encrypt-once` that allows the user to encrypt the secret data once and keep the encrypted data in the repository. The SecretFingerprint will be generated and stored locally in the developer's environment and strictly must not commit to the repository. Please consult the `.gitignore` file to exclude the `secrets.*.fp.yaml` files.
Loading