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

Allow to optionally use AppRole to authenticate with Vault #22

Merged
merged 1 commit into from Jul 21, 2022

Conversation

lonelyCZ
Copy link
Contributor

Signed-off-by: lonelyCZ 531187475@qq.com

Fixes #18

@lonelyCZ
Copy link
Contributor Author

Hi @irbekrm , thanks for your suggestions, I have added this feature.

/assign @irbekrm

@lonelyCZ
Copy link
Contributor Author

/hold

I will rebase this pr firstly.

@lonelyCZ
Copy link
Contributor Author

/unhold

@lonelyCZ
Copy link
Contributor Author

PTAL

/cc @irbekrm

Copy link
Contributor

@irbekrm irbekrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @lonelyCZ this is really good work 👍🏼

I have tested it with both authentication methods and everything worked as expected.

I have added a couple suggestions.
I think also we want to update the Readme in ./cm-vault with the available auth methods and update other details there like ClusterIssuer name etc. I also see that the Readme has out-of-date info about configuring port-forward in the kind cluster.

Apart from that, this looks good to go in, again great work!

cm-vault/vault-config/main.tf Outdated Show resolved Hide resolved
cm-vault/vault-config/main.tf Outdated Show resolved Hide resolved
cm-vault/cm-config/main.tf Show resolved Hide resolved
cm-vault/vault-config/variables.tf Outdated Show resolved Hide resolved
Signed-off-by: lonelyCZ <531187475@qq.com>
@irbekrm irbekrm added the area/vault Related to Vault installation workflow label Jul 21, 2022
@lonelyCZ
Copy link
Contributor Author

Thanks for your suggestion. I have updated it.

I think also we want to update the Readme in ./cm-vault with the available auth methods and update other details there like ClusterIssuer name etc. I also see that the Readme has out-of-date info about configuring port-forward in the kind cluster.

Thanks for pointing out. I will update the README in next pr.

@irbekrm
Copy link
Contributor

irbekrm commented Jul 21, 2022

Thanks @lonelyCZ !

This now looks good to me. Would be good to update Readme next, really it should be done at the same time as the change is added to code as else the Readme stays incorrect.

/lgtm
/approve

@jetstack-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irbekrm, lonelyCZ

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jetstack-bot jetstack-bot merged commit 9fb02ac into cert-manager:master Jul 21, 2022
@lonelyCZ
Copy link
Contributor Author

Would be good to update Readme next, really it should be done at the same time as the change is added to code as else the Readme stays incorrect.

I see, thanks, I will do it in future.

@lonelyCZ lonelyCZ deleted the pr-multi-auth branch July 26, 2022 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow to optionally use AppRole to authenticate with Vault
3 participants