KMS-653: Add a client-id to all KMS calls

[htranho]

Overview

What is the feature?

Add a client-id to all KMS calls

What is the Solution?

Add a client-id in headers to all KMS call

What areas of the application does this impact?

KeywordManager calls to KMS to fetch, update, insert and delete keywords. Also publish a new keyword version.

Testing

Request headers to kms should have as 'client-id' 'mmt-keyword-manager-$env'

Attachments

N/A

Checklist

• I have added automated tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.15%. Comparing base (c681ac5) to head (07256b7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1465   +/-   ##
=======================================
  Coverage   98.15%   98.15%           
=======================================
  Files         437      438    +1     
  Lines        7201     7204    +3     
  Branches     1544     1545    +1     
=======================================
+ Hits         7068     7071    +3     
  Misses        132      132           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cgokey]

maybe keywordManagerClientId for the name?

[htranho]

Done, updated

[eudoroolivares2016]

Kind of confused about this. Why do we need the proxy to pass the extra header?

[htranho]

The extra header, somehow, trigger CORS, so the proxy needed for local dev. In other env, 'kmsHost' is overwritten by the bamboo deployment script.

[htranho]

The issue came up as I test client-id on my local MMT pointing to cmr.sit.