Fix usage of endpoint in-call http tasks

[matthias-pichler]

Signed-off-by: Matthias Pichler m.pichler@warrify.com

Please specify parts of this PR update:

• Specification
• Schema
• Examples
• Extensions
• Use Cases
• Community
• CTK
• Other

Discussion or Issue link:

What this PR does:

The DSL describes the callHttp endpoint property as:

An URI or an object that describes the HTTP endpoint to call.

However:

1. many examples used a uri field directly in call http tasks
2. the schema did not allow to specify a string directly

so I fixed both

Additional information:

[cdavernas]

LGTM! Cheers!

[ricardozanini]

Sorry to be a PITA, but can you add an example? I think ours only has this structure:

endpoint:
    uri: ...

[matthias-pichler]

Sorry to be a PITA, but can you add an example? I think ours only has this structure:

endpoint:
    uri: ...

Sorry to be a PITA, but can you add an example? I think ours only has this structure:

endpoint:
    uri: ...

no worries ... added an example 👍

[ricardozanini]

I think in this case the format is uri-template since we want to support dynamic calls within the task.