> 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/sample-pipeline.md).

# Sample Pipeline

Purpose of providing the [sample pipeline](https://github.com/openMF/ph-ee-env-template/blob/master/.circleci/config.yml) is to ease the process in multiple ways :-

* Show evidence that the deploy, configure and test scripts mentioned in the installation instructions are in working state.
* If  [pipeline secrets are configured](https://app.gitbook.com/o/-L_J6oxbPK3wAuGnofJl/s/-L_J6oxfkTjM9Go4YNSW/~/changes/103/payment-hub-ee/overview/installation-instructions/secrets-to-be-configured-in-contexts-for-circleci) in the pipeline tool(eg. CircleCI) and you are using AWS EKS as your cloud, then the scripts using CircleCI orbs need only one change :-
  * Official helm charts and unreleased latest helm chart are currently hosted in fynarfin.io file system. Depending on your use case and audience type, take a decision on whether you are setting up for continuous configuration changes and which version/unreleased version you should use.
  * Since CircleCI helm orb doesn't accept a local file system path, deployment step needs a hosted helm chart.You can host you helm chart in you preferred chart hosting method (sample pipeline script shows how to upload to tomcat in amazon linux VM). Here is an alternative way :-

    ```
    aws s3 cp test.txt s3://mybucket/test2.txt
    ```
  *   Note that artifact hub points to fynarfin.io index.yaml for the charts. In chart.yaml or/and point CircleCI helm orb to your hosted chart URI.
* Reference pipeline is AWS specific and corresponding sections for authenticating in to you cloud service provider and getting the kubeconfig have to be replaced. How to replace those sections in the pipeline is outside the scope of the document.  


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mifos.gitbook.io/docs/payment-hub-ee/overview/installation-instructions/sample-pipeline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.