build(seaweedfs): stop make update when the [grpc.s3] backport lands

The backport becomes redundant once the vendored chart reaches 4.46.
Re-applied to a chart that already carries the section, BSD patch takes
it as reversed, removes the section and exits 0, so a re-vendor would
quietly return the s3 gRPC listener to plaintext. --forward refuses an
already-applied patch with a non-zero exit, which stops the update at
the point where the patch should be dropped.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
This commit is contained in:
Alexey Artamonov committed 2026-11-05 21:04:01 +03:00
1 parent a70a1cf83b
commit c3d1a73d8c
1 file changed
+5 -1
+5 -1
View File
@@ -61,7 +61,11 @@ update:
patch --no-backup-if-mismatch -p4 < patches/s3-service-name.patch
patch --no-backup-if-mismatch -p4 < patches/s3-service-name-consumers.patch
patch --no-backup-if-mismatch -p4 < patches/cluster-scoped-names-per-namespace.patch
patch --no-backup-if-mismatch -p4 < patches/s3-grpc-tls.patch
# Backport of seaweedfs/seaweedfs#11157, released in 4.46: drop the patch
# once the vendored chart carries [grpc.s3]. --forward makes that point
# fail here, where BSD patch would otherwise reverse it and remove the
# section without an error.
patch --forward --no-backup-if-mismatch -p4 < patches/s3-grpc-tls.patch
#patch --no-backup-if-mismatch -p4 < patches/retention-policy-delete.yaml
$(MAKE) update-image