ZKUI-392: implement veeam table with useChainedMutations

[ChengYanJin]

No description provided.

[bert-e]

Hello chengyanjin,

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.

Status report is not available.

[bert-e]

Incorrect fix version

The Fix Version/s in issue ZKUI-392 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 2.2.0

Please check the Fix Version/s of ZKUI-392, or the target
branch of this pull request.

[bert-e]

Waiting for approval

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

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @JBWatenbergScality

• @MonPote

• @ChengYanJin

[bert-e]

Conflict

There is a conflict between your branch feature/ZKUI-392-implement-veeam-configuration-UI-with-real-api-call and the
destination branch development/2.2.

Please resolve the conflict on the feature branch (feature/ZKUI-392-implement-veeam-configuration-UI-with-real-api-call).

git fetch && \
git checkout origin/feature/ZKUI-392-implement-veeam-configuration-UI-with-real-api-call && \
git merge origin/development/2.2

Resolve merge conflicts and commit

git push origin HEAD:feature/ZKUI-392-implement-veeam-configuration-UI-with-real-api-call

[bert-e]

Waiting for approval

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

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @ChengYanJin

• @MonPote

• @JBWatenbergScality

[bert-e]

Waiting for approval

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

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @MonPote

• @ChengYanJin

• @JBWatenbergScality

[codecov-commenter]

Codecov Report

Attention: 16 lines in your changes are missing coverage. Please review.

Comparison is base (19fb7f6) 59.19% compared to head (ffe1a90) 59.81%.

Files	Patch %	Lines
src/react/DataServiceRoleProvider.tsx	28.57%	10 Missing ⚠️
src/react/ui-elements/Veeam/VeeamTable.tsx	80.00%	2 Missing ⚠️
src/react/utils/testUtil.tsx	80.00%	2 Missing ⚠️
src/react/ui-elements/Veeam/VeeamConfiguration.tsx	85.71%	0 Missing and 1 partial ⚠️
src/react/ui-elements/Veeam/VeeamSummary.tsx	0.00%	1 Missing ⚠️

Additional details and impacted files

@@                 Coverage Diff                 @@
##           development/2.2     #685      +/-   ##
===================================================
+ Coverage            59.19%   59.81%   +0.62%     
===================================================
  Files                  218      219       +1     
  Lines                10459    10542      +83     
  Branches              3010     3027      +17     
===================================================
+ Hits                  6191     6306     +115     
+ Misses                4251     4219      -32     
  Partials                17       17              

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

[bert-e]

Waiting for approval

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

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @ChengYanJin

• @JBWatenbergScality

• @MonPote

[JBWatenbergScality]

LGTM !!

[ChengYanJin]

/approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/2.2

The following branches will NOT be impacted:

• development/1.4
• development/1.5
• development/1.6
• development/2.0
• development/2.1

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

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

• ✔️ development/2.2

The following branches have NOT changed:

• development/1.4
• development/1.5
• development/1.6
• development/2.0
• development/2.1

Please check the status of the associated issue ZKUI-392.

Goodbye chengyanjin.