single-servicebc-correios.secrets.RABBITMQ_PASS, RABBITMQ_URL, and ENCRYPTION_KEY. The PostgreSQL password is not operator-provided with the bundled subchart: the Bitnami postgresql subchart auto-generates it into the <release>-postgresql Secret (key password) and the app reads it via secretKeyRef. Set bc-correios.secrets.POSTGRES_PASSWORD only for an external PostgreSQL (postgresql.external=true) without postgresql.auth.existingSecret.bc-correios.configmap.*_HOST/CACHE_ADDR/OBJECT_STORAGE_ENDPOINT only when pointing at external/overridden endpoints.github.com/LerianStudio/helm; license is Apache-2.0.Helm chart for deploying the BC Correios plugin service.
helm dependency build ./charts/plugin-bc-correios
helm upgrade --install plugin-bc-correios ./charts/plugin-bc-correios \
--namespace plugin-bc-correios --create-namespace \
--values ./charts/plugin-bc-correios/values-template.yaml
RABBITMQ_PASS, RABBITMQ_URL) and ENCRYPTION_KEY before install. The bundled PostgreSQL and Valkey passwords are auto-generated by their subcharts and read via secretKeyRef; to pin them, set postgresql.auth.* / valkey.auth.* or supply postgresql.auth.existingSecret / valkey.auth.existingSecret.bc-correios.configmap for service URLs, telemetry, and plugin runtime settings.bc-correios.useExistingSecret when production secrets are managed outside Helm.This chart depends on PostgreSQL, RabbitMQ, and Valkey subcharts. Run helm dependency build before rendering or installing from a local checkout.
See the root repository documentation for release and chart maintenance workflows.