> For the complete documentation index, see [llms.txt](https://archivedocs.stackstate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archivedocs.stackstate.com/5.1/develop/developer-guides/stackpack/prepare_multi-instance_provisioning_script.md).

# Prepare a multi-instance provisioning script

A multi-instance StackPack requires a provisioning script that's able to provision multiple StackPack instances. To achieve that, you need a separate template file in the context for both `stackPack` and `instance`; `stackPack` needs to be provided with the `shared-template.stj`, and `instance` requires the `instance-template.stj` as in the example below:

Note that `instance-template.stj` has some instance specific information, like `topicName`, `instanceId` and anything else defined in `templateArguments`, while `shared-template` passes without any specifics (`[:]`).

```
import com.stackstate.stackpack.ProvisioningScript
import com.stackstate.stackpack.ProvisioningContext
import com.stackstate.stackpack.ProvisioningIO
import com.stackstate.stackpack.Version

class Provision extends ProvisioningScript {

  Provision(ProvisioningContext context) {
      super(context)
  }

  @Override
  ProvisioningIO<scala.Unit> install(Map<String, Object> config) {
    def instance_url = instanceURL(config)
    def templateArguments = [
                'topicName': topicName(config),
                'instance_url': instance_url,
                'instanceId': context().instance().id()
                ]
    templateArguments.putAll(config)

    return context().stackPack().importSnapshot("templates/shared-template.stj", [:]) >>
           context().instance().importSnapshot("templates/instance-template.stj", templateArguments)
  }

  @Override
  ProvisioningIO<scala.Unit> upgrade(Map<String, Object> config, Version current) {
    return install(config)
  }

  @Override
  void waitingForData(Map<String, Object> config) {
    context().sts().onDataReceived(topicName(config), {
      context().sts().provisioningComplete()
    })
  }

  private def topicName(Map<String, Object> exampleConfig) {
    def instance_url = exampleConfig.test_instance_url
    def topic = instance_url.replace("/", "_").replace(":", "_")
    return context().sts().createTopologyTopicName("example", topic)
  }

  private def instanceURL(Map<String, Object> exampleConfig) {
      def url = exampleConfig.test_instance_url
      def instance_url = ''
      if (url.startsWith('http') || url.startsWith('https')){
        instance_url = url.split("//")[1].split("/")[0]
      }
      else{
        instance_url = url.split("/")[0]
      }
      return instance_url
  }

}
```

The last step is to [prepare a StackPack `.sts` package and upload it to StackState.](/5.1/develop/developer-guides/stackpack/prepare_multi-instance_provisioning_script.md)


---

# 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://archivedocs.stackstate.com/5.1/develop/developer-guides/stackpack/prepare_multi-instance_provisioning_script.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.