> For the complete documentation index, see [llms.txt](https://mifos.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mifos.gitbook.io/docs/payment-hub-ee/overview/installation-instructions/post-deployment-steps.md).

# Post Deployment Steps

The Post\_installation\_Job is automated through a Kubernetes job in the helm chart. it will create secrets for ElasticSearch and Kibana. and Upload the BPMN. However, The following steps can be used to create Secrets and upload BPMN Manually.

* **Create the required secrets:**
  * Use <https://github.com/openMF/ph-ee-env-labs/tree/master/helm/es-secret> and <https://github.com/openMF/ph-ee-env-labs/tree/master/helm/kibana-secret> you can create a secret for Elasticsearch and Kibana. The command used to create a secret is
    * `make secrets`
  * Also to create a bulk-processor secret you can refer to CircleCI steps from config.yaml- <https://github.com/openMF/ph-ee-env-labs/blob/master/.circleci/config.yml>
* [Upload BPMN](https://app.gitbook.com/o/-L_J6oxbPK3wAuGnofJl/s/-L_J6oxfkTjM9Go4YNSW/~/changes/116/payment-hub-ee/overview/installation-instructions/configuration-instructions/deploy-bpmns-with-multiple-dfsp-ids)

**Helm Test -**&#x20;

* The `helm test` command runs the tests for a release. The argument this command takes is the name of a deployed release. The tests to be run are defined in the chart that was installed. `eg: helm test <release-name> --namespace <namespace>`

<pre class="language-yaml"><code class="lang-yaml"><strong>ex: helm test g2p-sandbox --filter name=g2p-sandbox-test-gov --namespace paymenthub 
</strong></code></pre>

* The test result reports can be either stored locally or can be stored in CircleCI containers using `store_test_results`&#x20;