Why is the prefixed "chore" and not "feature"?

Right, let's change it back to feat, I initially decided to make it a chore because I was considering to split the implementation in several PRs and only get a QA approval for the last one. However, we added more functions in this PR so it makes sense to call it a feature and require QA approval.

I tried to test this, but couldn't get it working. I used camunda platform connectors-8.7.0-alpha2. I did a maven clean
install in connectors. I used desktop modeler with this BPMN:

This would not work as we decided not to implement the FEEL part yet. For now, if you want to invoke an operation, you need to provide the whole payload in the input, i.e.:

{
  
  "camunda.operation.type": "base64",
  "params": ["test123"]
}

QA information

Test Environment

• Test required in (you can check both):
  • SaaS
  • SM
• Create a new test for this feature in our Pre Release Tests for @Szik to be able to test

Test Scope

Please describe the test scope, happy path, edge cases that come to your mind, and whatever you think might relevant to test

Test Data

Please provide the test data, if needed (files, URLs, code snippets, FEEL expressions)

@ztefanie it should work now, just a heads up that I also just changed the discriminator field name from operation to function so the payload should look like this now:

{
  
  "camunda.function.type": "base64",
  "params": ["test123"]
}

🚀 Deployment Results 🚀

Please find below the results of the latest deployments.

connectors-intrinsic-opera-c8sm

• Status: ❌
• ArgoCD: 🔗 Link(degraded resources)
• Deployment Jobs: 📋 Link
• Troubleshooting Tips: 🛟

Typical Errors
--------------
- ErrImagePull / ImagePullBackOff - The CI hasn't finished building the image yet or the image build has failed
  - Check whether the build is still in progress
    - If it is then increase "argocd_wait_for_sync_timeout"
    - If the build has failed then check the CI for the possible cause of the error
- Readiness / Liveness probe failed - The container is not fully functional yet
  - There could be many causes for this error, so there's no a single good solution for the problem
    - The best generic approach is to check the ArgoCD App for the underlying problems using the link above
      - Click on the problematic component and investigate "EVENTS" and "LOGS" tabs for clues
    - It could also be simply happening because, although everything seems to be correct, the app is not fully functional yet
      - In this case simply increase "argocd_wait_for_sync_timeout" value

• Details for Troubleshooting: 🛟

Kubernetes events
-----------------

🔧 Troubleshooting 🔧

The 🔗 ArgoCD link can be used to check the state and configuration of all the services deployed as part of the preview environments and get logs.

In case of error, please check 📋 Deployment Jobs and 🔗 ArgoCD to debug, and check our (yet to come) troubleshooting page