Feat/dataprotection -- Tests & Docs

[GilTeraSky]

1. What this PR does / why we need it

   This PR is the final in the series of Data Protection resources task.
   It includes tests and docs for data protection enablement, target location and backup schedule resources and data sources.

2. Which issue(s) this PR fixes

3. Additional information

4. Special notes for your reviewer

   For running the acceptance tests it is required to have 2 environment variables:
   TMC_MANAGED_CREDENTIALS_NAME - this variable should be a name of a TMC managed credentials which is required for
   running the tests. Although it is possible to create a TMC managed credentials via the resource, there is a necessity for the
   credentials to include a valid IAM role because when creating a target location with this type of credentials it fails if the IAM
   role doesn't have permissions.

   AZURE_CREDENTIALS_NAME - this variable should be a name of a azure self provisioned credentials which is required for
   running the tests. It is not supported creating azure self provisioned credentials for data protection use case.

[codecov-commenter]

Codecov Report

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

Comparison is base (d698e14) 25.41% compared to head (1f1dee6) 25.40%.

Additional details and impacted files

@@                   Coverage Diff                   @@
##           feat/dataprotection     #280      +/-   ##
=======================================================
- Coverage                25.41%   25.40%   -0.01%     
=======================================================
  Files                      155      155              
  Lines                    13601    13605       +4     
=======================================================
  Hits                      3457     3457              
- Misses                    9987     9991       +4     
  Partials                   157      157              

Files	Coverage Δ
internal/helper/handler_context.go	0.00% <0.00%> (ø)

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

[vmwclabot]

@GilTeraSky, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit f1de77e must be signed by [email protected]

[vmwclabot]

@GilTeraSky, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit f1de77e must be signed by [email protected]

[vrabbi]

LGTM

[ramya-bangera]

@GilTeraSky - Add mock tests too for data protection feature, you can refer akscluster resource, but you can take it up after utkg work

[ramya-bangera]

Is there a usage for this file?

[GilTeraSky]

I put this in the folder so it will be easy to test from this folder, should I remove it?

[GilTeraSky]

@GilTeraSky - Add mock tests too for data protection feature, you can refer akscluster resource, but you can take it up after utkg work

We already agreed that with the Converter there is no need to mock anything and we should add tests for the converter in the future by me or someone else.

[ramya-bangera]

We already agreed

When I say mock test, it Is mimicking the server with custom request/response so that we can cover even edge cases which we usually can't cover with the actual server. let me know if need more details

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.