Project generator could create a bit nicer unique component aliases

[zregvart]

Our component aliases currently contain connectionId, which is not too user friendly (for example twitter-mention-connector--KuYUr3kEMhDH0Nq8VGV). We could generate aliases by following two simple rules

• for components that do not occur more than once, don't use aliases
• for components that occur more than once use a per component counter

This should lead to component aliases that look something like this in the generated syndesis.yml:

---
flows:
- steps:
  - kind: endpoint
    uri: twitter-mention-connector:MENTIONS
  - kind: endpoint
    uri: atlas:mapping-step-2.json
  - kind: endpoint
uri: salesforce-upsert-sobject-1?sObjectIdName=TwitterScreenName__c&sObjectName=Contact
  - kind: endpoint
uri: salesforce-upsert-sobject-2?sObjectIdName=TwitterScreenName__c&sObjectName=Opportunity

[lburgazzoli]

This would generate a little bit of inconsistency in secrets as it would result in something like:

twitter-mention-connector.clientId = ...
twitter-mention-connector.clisnetSecret = ...

salesforce-upsert-sobject.configurations.salesforce-upsert-sobject-1.userName = ...
salesforce-upsert-sobject.configurations.salesforce-upsert-sobject-1.password = ...

salesforce-upsert-sobject.configurations.salesforce-upsert-sobject-2.userName = ...
salesforce-upsert-sobject.configurations.salesforce-upsert-sobject-2.password = ...

So there is something that uses the configurations syntax and something not, is that ok ?

[zregvart]

Any thoughts on the comment above @iocanel @jimmidyson @rhuss @KurtStam?

[zregvart]

@lburgazzoli I think that would be ok, as most integrations I think would use only single connection.

[lburgazzoli]

If Zoran's solution looks ok I can work on this tomorrow (so it can solve #660)