Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for enabling TLS and handling server CA cert. #509

Closed
wants to merge 0 commits into from

Conversation

andrewj-a42
Copy link
Contributor

@andrewj-a42 andrewj-a42 commented Aug 1, 2023

Description of your changes

The change is adding support for enabling 'SERVER_AUTHENTICATION' for the TransitEncryptionMode.
The code is setting the value of TransitEncryptionMode field for gcp client and is observing serverCACerts field.
As soon as the instance is provisioned and CA is generated it is added to the managed resource to the atProvider section.

Fixes #

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

This code was tested by building a fresh image and deploying it to a dev cluster with crossplane pod up and running.
Successful cloudMemoryStore provisioning was performed and with TransitEncryptionMode field set to 'SERVER_AUTHENTICATION' value, the redis provisioning process generated server CA certificate which became part of 'atProvider' section of the managed resource.

@dee0sap
Copy link
Collaborator

dee0sap commented Aug 22, 2023

Hello @hasheddan & @Feggah

I am following up on this PR on behalf of the author who is my teammate and who is on vacation.

I think with the announcement the other day, upbound devs no longer contributing to community providers, this PR went into limbo as the only reviewer so far was @ezgidemirel. If/when you have a moment would you please provide a review?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants