[bitnami/argo-workflow-cli] Release argo-workflow-cli-3.6.0-debian-12-r0 (#74921)

Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-11-15 12:27:13 +01:00
committed by GitHub
parent 1bffaf37e8
commit 850d9d1f73
4 changed files with 9 additions and 9 deletions

View File

@@ -15,7 +15,7 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"argo-workflows-3.5.12-1-linux-${OS_ARCH}-debian-12" \
"argo-workflows-3.6.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -38,13 +38,13 @@ ENV OS_ARCH="${TARGETARCH:-amd64}"
LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
org.opencontainers.image.base.name="scratch" \
org.opencontainers.image.created="2024-11-07T01:40:21Z" \
org.opencontainers.image.created="2024-11-15T11:10:37Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.5.12-debian-12-r1" \
org.opencontainers.image.ref.name="3.6.0-debian-12-r0" \
org.opencontainers.image.title="argo-workflow-cli" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="3.5.12"
org.opencontainers.image.version="3.6.0"
COPY prebuildfs /
COPY rootfs /
@@ -54,7 +54,7 @@ COPY --from=builder /opt/bitnami/argo-workflows/hack/ssh_known_hosts /etc/ssh/ss
COPY --from=builder /opt/bitnami/argo-workflows/.spdx-argo-workflows.spdx /opt/bitnami/argo-workflows/.spdx-argo-workflows.spdx
COPY --from=builder /opt/bitnami/argo-workflows/licenses /opt/bitnami/argo-workflows/licenses
ENV APP_VERSION="3.5.12" \
ENV APP_VERSION="3.6.0" \
BITNAMI_APP_NAME="argo-workflow-cli"
USER 1001

View File

@@ -3,6 +3,6 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "3.5.12-1"
"version": "3.6.0-0"
}
}

View File

@@ -1,5 +1,5 @@
rolling-tags:
- "3"
- 3-debian-12
- 3.5.12
- 3.6.0
- latest

View File

@@ -30,11 +30,11 @@ Deploying Bitnami applications as Helm Charts is the easiest way to get started
## Why use a non-root container?
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-work-with-non-root-containers-index.html).
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
## Supported tags and respective `Dockerfile` links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-understand-rolling-tags-containers-index.html).
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`.