Deploying scripts

[jessewindebank1809]

Hi @michal-kapala,

This is brilliant thanks for sharing!

Have you found a streamlined process to deploy scripts to a Jitterbit project from VS code or you having to copy and paste into Jitterbit Studio?

[michal-kapala]

@jessewindebank1809 thank you, the extension is in early development, the main priority is to add static error checking for scripts (script-wide scope only). As of now there are no project management/deployment features or cross-script checking.

Jitterbit stores all objects including scripts in XML format, you can find them in Jitterbit Studio's directory at /projects/<project dir>/<environment dir>/Data/Script. Here's an example one:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Entity type="Script">
  <Header Deleted="false" DeployDirty="true" Deployed="false" HasMoved="false" ID="05011b25-d341-4ca5-9f32-42ee41f2f286" Name="Read Output">
    <konga.string name="Description"/>
  </Header>
  <Properties>
    <Item key="script_id" value="03021b25-d341-4ca5-9f32-42ee41f2f286"/>
  </Properties>
  <konga.string name="script">
    &lt;trans&gt;
    ReadFile("s.a7347471-ace8-4fc3-b549-7c673523031b")
    &lt;/trans&gt;
  </konga.string>
</Entity>

For direct cloud deployment the extension would need to hit Jitterbit APIs to authenticate to Harmony and then upload the changes. I don't think Jitterbit has any API integration guide on this and I'm not even sure they would be okay with that as this is not an affiliated project.

I did consider export to local environment as a potential feature so that VS Code could generate the XML files and place them in the selected Jitterbit Studio workspace, project and environment. That way you wouldn't need to copy the code back and forth between the two editors, cloud deployment would still require Jitterbit Studio.

That's just a very far future idea, for now the parser and interpreter still need a lot of language features and error handling implementation

[michal-kapala]

I've created a GitHub project for a better overview and tracking of the features

[jessewindebank1809]

Thanks @michal-kapala

Agreed, a conversion process would be the simplest way to go from vscode into the local Jitterbit project.

The Jitterbit collection of REST APIs do not currently support uploading specific project artifacts from what I see.

[michal-kapala]

I created jitterbit-extractor as a standalone solution for project code import into source files, the functionality will probably be moved over to the extension later.