[bitnami/rabbitmq] Release 3.10.22-debian-11-r2 (#32819)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-05-06 00:41:49 +01:00 committed by GitHub
parent 634cabb34e
commit ca2d91b4df
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 13 additions and 9 deletions

View File

@ -2,12 +2,11 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:109c7d51bd69bb6b3df71017440c1ea0699454f81fe188056c083f0b57c96ea6" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-05-02T22:18:14Z" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-05-05T22:53:07Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="3.10.22-debian-11-r1" \
org.opencontainers.image.ref.name="3.10.22-debian-11-r2" \
org.opencontainers.image.title="rabbitmq" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="3.10.22"
@ -24,7 +23,7 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libgcc-s1 libssl1.1 libstdc++6 libtinfo6 locales procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"erlang-25.3.1-0-linux-${OS_ARCH}-debian-11" \
"erlang-25.3.2-0-linux-${OS_ARCH}-debian-11" \
"rabbitmq-3.10.22-0-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \

View File

@ -3,7 +3,7 @@
"arch": "amd64",
"distro": "debian-11",
"type": "NAMI",
"version": "25.3.1-0"
"version": "25.3.2-0"
},
"rabbitmq": {
"arch": "amd64",

View File

@ -412,11 +412,16 @@ generate_random_string() {
ascii)
filter="[:print:]"
;;
numeric)
filter="0-9"
;;
alphanumeric)
filter="a-zA-Z0-9"
;;
numeric)
filter="0-9"
alphanumeric+special|special+alphanumeric)
# Limit variety of special characters, so there is a higher chance of containing more alphanumeric characters
# Special characters are harder to write, and it could impact the overall UX if most passwords are too complex
filter='a-zA-Z0-9!@#$%^'
;;
*)
echo "Invalid type ${type}" >&2
@ -647,4 +652,4 @@ run_chroot() {
else
chroot --userspec="$userspec" / bash -c "cd ${cwd}; export HOME=${homedir}; exec \"\$@\"" -- "$@"
fi
}
}