Deploy Metadata in Backbeat tests

[Kerkesni]

• Deploy a metadata setup in a separate CI job
• Add a minimal test for queue populator that uses the metadata backend

Issue: BB-496

[bert-e]

Hello kerkesni,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.18%. Comparing base (d963e52) to head (2b10733).
Report is 7 commits behind head on development/9.0.

Additional details and impacted files

see 13 files with indirect coverage changes

Components	Coverage Δ
Bucket Notification	75.37% <ø> (ø)
Core Library	79.74% <ø> (+3.47%)	⬆️
Ingestion	70.14% <ø> (ø)
Lifecycle	77.08% <ø> (+0.89%)	⬆️
Oplog Populator	85.06% <ø> (ø)
Replication	58.64% <ø> (+0.84%)	⬆️
Bucket Scanner	85.60% <ø> (ø)

@@                 Coverage Diff                 @@
##           development/9.0    #2610      +/-   ##
===================================================
+ Coverage            71.41%   73.18%   +1.77%     
===================================================
  Files                  201      201              
  Lines                13366    13366              
===================================================
+ Hits                  9545     9782     +237     
+ Misses                3811     3574     -237     
  Partials                10       10              

Flag	Coverage Δ
api:retry	9.48% <ø> (ø)
api:routes	9.30% <ø> (ø)
bucket-scanner	85.60% <ø> (ø)
ft_test:queuepopulator	10.42% <ø> (?)
ingestion	12.56% <ø> (ø)
lib	7.33% <ø> (-0.01%)	⬇️
lifecycle	18.76% <ø> (ø)
notification	1.07% <ø> (ø)
replication	18.54% <ø> (ø)
unit	48.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[bert-e]

Conflict

There is a conflict between your branch improvement/BB-496 and the
destination branch development/9.0.

Please resolve the conflict on the feature branch (improvement/BB-496).

git fetch && \
git checkout origin/improvement/BB-496 && \
git merge origin/development/9.0

Resolve merge conflicts and commit

git push origin HEAD:improvement/BB-496

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[francoisferrand]

should these not be just another "functional" test? (folder & ft_test:queuepopulatoryarn target)

• it is not really "end-2-end", since we still deploy (some) mocks, and do not use the same deployment as in the product
• it is similar to the funcitonal tests, in the sense that we run an "real" backbeat service, and the tests are running in separate process
• it does not replace (or try to) the actual e2e tests we have in Zenko

[bert-e]

Conflict

There is a conflict between your branch improvement/BB-496 and the
destination branch development/9.0.

Please resolve the conflict on the feature branch (improvement/BB-496).

git fetch && \
git checkout origin/improvement/BB-496 && \
git merge origin/development/9.0

Resolve merge conflicts and commit

git push origin HEAD:improvement/BB-496

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[Kerkesni]

/approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/9.0

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.6

Please check the status of the associated issue BB-496.

Goodbye kerkesni.

The following options are set: approve