Adding flow step to API provider based integration yields error

[zregvart]

This is a...

[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Documentation issue or request

The problem

I can't seem to edit a flow to add a step to it. The browser console emits an error:

main.bd08e7b5ad2ce0b417ba.js:1 TypeError: Cannot read property 'action' of undefined
    at n.ngOnChanges (11.bb2047dff352bcbffb47.js:1)
    at main.bd08e7b5ad2ce0b417ba.js:1
    at main.bd08e7b5ad2ce0b417ba.js:1
    at $a (main.bd08e7b5ad2ce0b417ba.js:1)
    at Sl (main.bd08e7b5ad2ce0b417ba.js:1)
    at Object.updateDirectives (11.bb2047dff352bcbffb47.js:1)
    at Object.updateDirectives (main.bd08e7b5ad2ce0b417ba.js:1)
    at Xa (main.bd08e7b5ad2ce0b417ba.js:1)
    at il (main.bd08e7b5ad2ce0b417ba.js:1)
    at rl (main.bd08e7b5ad2ce0b417ba.js:1)

Expected behavior

I should be able to edit and add steps as needed to the flow.

Screenshot

Request and Response Data

API Endpoints and Schemas

I only see GET requests to /api/v1/integrations/i-LNUix7uR6BhTm3sXS83z and /api/v1/monitoring/integrations/i-LNUix7uR6BhTm3sXS83z, probably unrelated.

Tasks involved / Steps to Reproduce

1. Create API provider based integration
2. Try to edit one of the flows to add a step

console-log.txt

[oscerd]

I believe the set-body extension currently don't work if you compile with 1.5-SNAPSHOT syndesis dependencies.

[zregvart]

Perhaps it's an issue with Set Body extension, I can add the mapper to the POST request (one that has datashape on the start and end shapes)

[oscerd]

yes, the problem with setBody it's documented here: syndesisio/syndesis-extensions#69

Also we need to align the extensions to what we have in Syndesis.

[gashcrumb]

Page shouldn't be throwing that error anyways, will definitely fix that.

[gashcrumb]

Hmm, actually has nothing to do with the API provider or the set body extension, it occurs when the start connection doesn't have a data shape like the timer connection, so just a UI bug.

[tplevko]

@mmajerni please verify the fix

[mmajerni]

Verified by QE