Did we verify that api keys where accepted by metricbeat module ? This opened issue says otherwise elastic/beats#29271

After taking a look at metricbeat module it seems that it doesn't support api_key authorization which is also proven by the ticket Kevin linked above.

The change seems to be a bit bigger and separate from the scope of this ticket and I would suggest having a separate ticket for it.

The necessary changes as per my understanding are as follows:

1. Add APIKey string prop here which will hold the raw decoded api_key value.
2. Read the config api_key here similar to username and pass.
3. checking here if both Username, Password & api_key are both set then reject similar to this.
4. Keep cascading the api_key prop through the different functions similar to username and password so that you are able to access it here.
5. Add Auth header with the encoded api_key value, similar to what is done here and here.
6. We need to verify what should happen if both BearerTokenFile & APIKey are set, should we just overwrite the value with what we have in the api_key prop or reject similar to step 3.
7. Update affected tests

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

🤖 GitHub comments

🌐 Coverage report

LGTM. Let's create a follow up (or update the existing ticket with the findings) for adding api key support in metricbeat module