vmware / terraform-provider-tanzu-mission-control

Terraform provider to manage resources of Tanzu Mission Control
Mozilla Public License 2.0
38 stars 31 forks source link

Add opaque secret type #385

Closed warroyo closed 5 months ago

warroyo commented 5 months ago
  1. What this PR does / why we need it: This adds the ability to use opaque secret type with the k8s secret resource
vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

codecov-commenter commented 5 months ago

Codecov Report

Attention: Patch coverage is 18.26923% with 85 lines in your changes are missing coverage. Please review.

Project coverage is 25.23%. Comparing base (102b2ad) to head (d5171ca). Report is 2 commits behind head on main.

Files Patch % Lines
internal/resources/kubernetessecret/spec/spec.go 0.00% 35 Missing :warning:
...l/resources/kubernetessecret/spec/cluster_scope.go 41.46% 21 Missing and 3 partials :warning:
...rnal/resources/kubernetessecret/resource_secret.go 0.00% 18 Missing :warning:
...l/resources/kubernetessecret/data_source_secret.go 0.00% 8 Missing :warning:
Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #385 +/- ## ========================================== - Coverage 25.31% 25.23% -0.08% ========================================== Files 195 195 Lines 16845 16908 +63 ========================================== + Hits 4264 4267 +3 - Misses 12363 12423 +60 Partials 218 218 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

vmw-vjn commented 5 months ago

@AkbaraliShaikh - can you kindly review and add/append to this PR wrt TMC-56160

cc: @shobha2626 / @ramya-bangera

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

shobha2626 commented 5 months ago

@AkbaraliShaikh - can you kindly review and add/append to this PR wrt TMC-56160

cc: @shobha2626 / @ramya-bangera

@vmw-vjn Documentation and acceptance changes are missing in the PR. We would need them before making the release with this change

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

AkbaraliShaikh commented 5 months ago

@AkbaraliShaikh - can you kindly review and add/append to this PR wrt TMC-56160

cc: @shobha2626 / @ramya-bangera

@warroyo I have fixed/updated the following in my commit

Can you please update the acceptance tests?

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

vmwclabot commented 5 months ago

@warroyo, 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 <john.doe@email.org> 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.

AkbaraliShaikh commented 5 months ago

@AkbaraliShaikh / @warroyo could you pease share the screenshot of successful mock test and acceptance test screenshot?

image

image