You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current implementation of HTTP sinks lacks the flexibility to dynamically configure URLs and payloads, making it challenging to seamlessly integrate with existing APIs without establishing a rigid contract with Meteor. For example patching existing resource in guardian.
Describe the solution you'd like
I propose introducing templating support for both the URL and payload in HTTP sinks. This enhancement would empower users to dynamically configure endpoints and customize payloads based on specific requirements.
sinks:
name: httpconfig:
method: PATCHsuccess_code: 200url: https://example.com/v1beta1/{{.Urn}}headers:
some-header: some-valuescript:
engine: tengosource: | // global variable asset payload := { // do transformation here key1: asset.urn, ... } sink(payload)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current implementation of HTTP sinks lacks the flexibility to dynamically configure URLs and payloads, making it challenging to seamlessly integrate with existing APIs without establishing a rigid contract with Meteor. For example patching existing resource in guardian.
Describe the solution you'd like
I propose introducing templating support for both the URL and payload in HTTP sinks. This enhancement would empower users to dynamically configure endpoints and customize payloads based on specific requirements.
The text was updated successfully, but these errors were encountered: