Support for $SECRET in pipes

Completed

Follow

Marius Dammen

• October 23, 2020 11:00

I see that $ENV is supported in pipes, but it seems like $SECRET doesn't work, is that correct?

The context is sending an specific api key in a header for a specific GET/POST operation. That kind of value fits more into a $SECRET than to an $ENV, but must be configured in the pipe.

0

• 

  Tom Bech

  • October 28, 2020 11:01

  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

  • October 28, 2020 12:26

  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

  • October 30, 2020 14:45

  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

  • November 05, 2020 15:52

  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.