Enterprise Store charm reference

Configuration options

Option	Type	Default	Description
registration_bundle	string	null	Base64-encoded JSON generated by store-admin. It contains domain, private_key, public_key, store_id, and store_assertion.
certificate	string	null	PEM-encoded TLS certificate, or selfsigned when private_key has the same value.
private_key	string	null	Unencrypted PEM-encoded TLS private key, or selfsigned when certificate has the same value.
offline	boolean	false	Installs from the store-bundle resource and enables offline mode.

Integrations

Endpoint	Interface	Requirement	Behavior
database	postgresql_client	Required	Requests the superuser role and a database named enterprise-store.
haproxy-route	haproxy-route	Optional	Places the store behind HAProxy, which terminates TLS and routes to port 80.
s3-credentials	s3	Optional; required in offline mode	Supplies S3-compatible blob-storage configuration.
rollingops-peers	rollingops-peers	Internal peer relation	Coordinates rolling configuration, certificate, and snap changes across units.

Actions

Action	Description	Example
status	Returns the output of enterprise-store status.	juju run enterprise-store/leader status --wait
retry-install	Retries installation after the cause of an installation failure is corrected.	juju run enterprise-store/0 retry-install --wait

Resource

Resource	Type	Description
store-bundle	file	Offline tarball containing snapd, core22, and enterprise-store snaps with matching assertions. The initial bundle also contains proxy.assert.

Unit status messages

Status	Message	Meaning
Active	Running on: <registered-url>	The store is running without HAProxy.
Active	Fronted by haproxy at: <url>	The store is available through the HAProxy integration.
Maintenance	Installing application snap	The charm is installing the Enterprise Store snap.
Maintenance	Configuring application snap	The charm is applying snap configuration.
Maintenance	Waiting for rolling-ops lock	The unit is waiting to perform a coordinated rolling change.
Maintenance	Configuring haproxy-route relation	The charm is publishing its HAProxy route requirements.
Blocked	Missing database relation	No usable database connection is available.
Blocked	The unit is not registered, please supply a registration_bundle	Registration configuration is missing.
Blocked	The s3-credentials relation is not established	Offline mode requires the S3 integration.
Blocked	The store.assert has not been applied, check store-bundle resource	The initial offline resource did not supply an applicable store assertion.
Blocked	The store-bundle resource is missing or corrupted	The offline resource cannot be fetched.
Blocked	Failed to install the enterprise-store from the resource	Installation from the offline resource failed.
Blocked	Failed to install the enterprise-store	Online snap installation failed.
Blocked	Remove certificate/private_key config: TLS is terminated by haproxy when related via the haproxy-route interface	Charm-level and HAProxy TLS configuration conflict.

Other blocked messages can report invalid configuration, missing registration bundle keys, database creation failure, missing S3 fields, or failed snap and S3 configuration. Inspect juju status and juju debug-log for the complete message.