[FEATURE REQ] Backends Credentials Specified in Config Publisher Yaml file

[zcarroll4]

Please describe the feature.

Can we specify the backend's headers within the publisher configuration yaml files? Similar to how the example displays defining the credentials for the loggers?

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[guythetechie]

@zcarroll4 - the publisher configuration YAML should support most options in the REST API.

Have you tried something like this?

backends:
 - name: mybackend
   properties:
     credentials:
       ...etc

Here is the credentials object that the API expects.

[zcarroll4]

@zcarroll4 - the publisher configuration YAML should support most options in the REST API.

Have you tried something like this?

backends:

 - name: mybackend

   properties:

     credentials:

       ...etc

Here is the credentials object that the API expects.

This is exactly what I was looking for, I'll take a look at that wiki page tomorrow and test again. And yeah I tried something similar to how the logger syntax was but didn't have any luck yet.

[waelkdouh]

@zcarroll4 it would be great if you can post a scrubbed sample here for future references once you get a successful run.

[zcarroll4]

backends:
  - name:FUNC-APP-TX
    properties:
      url: "https://****************.azurewebsites.us/api"
      resourceid: "https://***********************/subscriptions/******************/resourceGroups/********/providers/Microsoft.Web/sites/*************"      
      credentials:
        header: 
          "HEADER-NAME-1": [
            "**************************************"
          ]
          "HEADER-NAME-2": [
            "{{INSERT SAVED NAME VALUE}}"
          ]