When deploying a sharded cluster of mongodb using terraform, integrations happen very quickly.
During this period the s3 integration is made (but its configurations are not set) , when the PBM status is retrieved inside the charm with charmed-mongodb.pbm status -o json, it results in {"Error":"get status of pitr: unable check PITR config status: get config: missed config"}, this error results in the charm showing a status of PBM error
when in fact it should result in something more informative. Perhaps a BlockedStatus("Missing configurations")
When deploying a sharded cluster of mongodb using terraform, integrations happen very quickly.
During this period the s3 integration is made (but its configurations are not set) , when the PBM status is retrieved inside the charm with
charmed-mongodb.pbm status -o json, it results in{"Error":"get status of pitr: unable check PITR config status: get config: missed config"}, this error results in the charm showing a status ofPBM errorwhen in fact it should result in something more informative. Perhaps a
BlockedStatus("Missing configurations")