Support for $SECRET in pipes

Planned

Comments

4 comments

  • Tom Bech

    Correct, currently $SECRET() in a pipe config is only supported specifically for certain encryption-related DTL functions.

    Could you add an example of how/where having support for $SECRET() would be useful in a pipe config? (I'm not entirely sure I understood your description)

    0
    Comment actions Permalink
  • Marius Dammen

    The example above would look something like this:

    "sink": {
    "type": "json",
    "system": "any-http-system",
    "headers": {
    "X-API-Key-For-Method": "$SECRET(my-service-method-key)"
    },
    "url": "/ServiceMethodProtectedByKey"
    },

    Without the $SECRET support, I will need to duplicate the number of systems to equal the number of methods. I consider this particular pattern an edge case, but cannot see the reason for the constraint. If it cannot be added, at least update the documentation with where $SECRET can (and cannot) be used.

    0
    Comment actions Permalink
  • Tom Bech

    Thanks! We have added this to our backlog (more specifically support for $SECRET() in the header property on the json (and rest) sink). I will notify you in this thread when it's merged to nightly and ready for testing.

    0
    Comment actions Permalink
  • Tom Bech

    This feature has now been implemented and should be available in tomorrow's "nightly" build.

    0
    Comment actions Permalink

Please sign in to leave a comment.