[bitnami/rmq-default-credential-updater] Release rmq-default-credential-updater-1.0.4-debian-12-r32 (#75491)

Signed-off-by: Bitnami Bot <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2024-12-04 04:29:59 +01:00 committed by GitHub
parent 761b700a09
commit f7e2de90b7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 6 additions and 6 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=( \
"rmq-default-credential-updater-1.0.4-21-linux-${OS_ARCH}-debian-12" \
"rmq-default-credential-updater-1.0.4-22-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@ -38,10 +38,10 @@ 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-07T08:40:01Z" \
org.opencontainers.image.created="2024-12-04T03:00:27Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="1.0.4-debian-12-r31" \
org.opencontainers.image.ref.name="1.0.4-debian-12-r32" \
org.opencontainers.image.title="rmq-default-credential-updater" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="1.0.4"

View File

@ -3,6 +3,6 @@
"arch": "amd64",
"distro": "debian-12",
"type": "NAMI",
"version": "1.0.4-21"
"version": "1.0.4-22"
}
}

View File

@ -26,7 +26,7 @@ Looking to use RabbitMQ Default User Credential Updater in production? Try [VMwa
## 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`.
@ -56,7 +56,7 @@ docker build -t bitnami/APP:latest .
## 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).
## Configuration