Invoking metadata endpoints for non dynamic actions

[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

In API provider integrations I noticed that we invoke /api/v1/connections/api-provider/actions/io.syndesis:api-provider-start and /api/v1/connections/api-provider/actions/io.syndesis:api-provider-end endpoints -- the action metadata. For actions that are not tagged with dynamic. The generated integration already contains the shapes based on the OpenAPI specification and invoking the action metadata endpoint for them will yield any data shape as that's what the connector descriptor defines.

Expected behavior

Invoking action metadata endpoint only for actions tagged with dynamic.

Tasks involved / Steps to Reproduce

1. Create API provider integration based on the TODO OpenAPI
2. While implementing one of the flows notice the invocations of /api/v1/connections/api-provider/actions/io.syndesis:api-provider-start and /api/v1/connections/api-provider/actions/io.syndesis:api-provider-end endpoints

[gashcrumb]

Should be easy enough to fix, those are done here.

[mastepan]

@gashcrumb please keep this open for the QE be able to track and verify. Thanks

[mastepan]

@gashcrumb I got back to this. Is there anything that QE should check? Or can we add ignore/QE label?

[tplevko]

This is related to the old UI, so not really relevant anymore. Closing with QE_ignore