Qualify the variable names in funktion.yml more

[chirino]

seems like we could get in trouble if 2 components use a field named the same

---
flows:
- steps:
  - kind: endpoint
    uri: twitter-mention:?accessToken={{accessToken}}&accessTokenSecret={{accessTokenSecret}}&consumerKey={{consumerKey}}&consumerSecret={{consumerSecret}}
  - kind: endpoint
    uri: atlas:mapping-step-2.json
  - kind: endpoint
    uri: salesforce-upsert-contact:?clientId={{clientId}}&clientSecret={{clientSecret}}&loginUrl=https://login.salesforce.com&refreshToken={{refreshToken}}

instead of {{accessToken}} perhaps we should be using something like {{twitter-mention.accessToken}}

[davsclaus]

Whatever the ipaas name those doesn't matter from Camel pov.

When you set {{accessToken} its looked up in some property placeholders like in application.properties. So the ipaas backend can prefix those with unique ids all day it want.

But the option name in Camel you cannot change its always called accessToken on that twitter-mention.

So you can change the uri in the funktion to be

accessToken={{somethingGoesHere-accessToken}}

to make it unique.

[chirino]

Fixed,