src
folder.TutorialProvision.groovy
)tutorial-component-template.json.handlebars
and tutorial-relation-template.json.handlebars
)Tutorial component id extractor.groovy
and Tutorial relation id extractor.groovy
)resources
directory)stackpack.conf
)src/main/stackpack
folder of the project..sts
that we can send to StackState. Since the .sts
file is essentially a ZIP archive, you can build the StackPack from the directory stackpack-tutorial/src/main/stackpack
in the sample repository using the command:conf.d
configuration folder in the directory it is running from. This may require you to run the CLI from a different location. If so, remember to use an absolute path to refer to the StackPack binary.src/main/stackpack/resources
directory). Install the StackPack with the Install button.curl
command to send it to StackState.curl
command shown in StackState contain data fields specific to your StackState installation, such as your API key and StackState URL.tutorial
label. This should result in a topology similar to the following:curl
command that is processed by StackStatestreams
part with the following code:tutorial-tutorial://tutorial-1-component-template
) among the templates. Check the checkbox in front of the template and use the Export Component Template Function button to export it.tutorial-component-template.json.handlebars
file in your StackPack. The export has a different structure than the file in our StackPack so we need to edit the file before updating the original. Specifically, the file in our StackPack contains only the handlebarsTemplate
property in the export.handlebarsTemplate
property\"
) with quote characters ("
)tutorial-template.stj
contains a DataSource
and Synchronization
and includes the contents of the separate templates and Groovy script files into a single JSON0.0.2
version of the StackPack. Upload the StackPack to StackState using the CLI.curl
command we used earlier and your upgrade is complete.