Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: ScriptTask conversion uses scriptFormat header instead of language #498

Open
jonathanlukas opened this issue Oct 26, 2023 · 1 comment · Fixed by #514
Open

Bug: ScriptTask conversion uses scriptFormat header instead of language #498

jonathanlukas opened this issue Oct 26, 2023 · 1 comment · Fixed by #514
Assignees
Labels

Comments

@jonathanlukas
Copy link
Collaborator

Describe the bug

If a script task is converted, the header used to define the scripting language is scriptFormat, just like it was in Camunda 7.
This is not compatible with the zeebe-script-worker which requires language

Steps to reproduce

  1. Define a Camunda 7 script task with inline script and script format
  2. Convert it
  3. The scriptFormat has become the header scriptFormat
  4. Run the process with the zeebe-script-worker
  5. it fails as no language is present

Expected Behaviour

The scriptFormat is translated to language

Library version

0.6.1

Camunda Platform 7 version

7.20.0

Camunda Platform 8 version

8.3.0

@ingorichtsmeier
Copy link
Contributor

As a follow-up: I've seen the issue mentioned in the release 0.8.0, and I'm wondering if the dependency to the script-worker, that is introduced here, is documented anywhere?

Maybe it's worth to provide an example for script migration? And explain which docker contain to integrate to the cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants