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

provider/chef: Migrate Chef to use KEY_MATERIAL rather than using a Pem file #10105

Merged
merged 1 commit into from
Nov 16, 2016

Conversation

stack72
Copy link
Contributor

@stack72 stack72 commented Nov 14, 2016

This will allow us to standardise on how we set KEY_MATERIAL

@jen20
Copy link
Contributor

jen20 commented Nov 16, 2016

This LGTM - it finishes the work that @phinze and I did a while back. However, we should update the documentation to make it clear that you need the key material and not a path.

file

This will allow us to standardise on how we set KEY_MATERIAL
@stack72 stack72 force-pushed the f-chef-key_material branch from 8e5f6ab to 50cab91 Compare November 16, 2016 17:03
@stack72
Copy link
Contributor Author

stack72 commented Nov 16, 2016

@jen20 documents updated as requested. Will merge when it goes green and @mitchellh has finished 0.8-beta

@stack72 stack72 merged commit e319d2c into master Nov 16, 2016
@stack72 stack72 deleted the f-chef-key_material branch November 16, 2016 17:12
@ghost
Copy link

ghost commented Apr 20, 2020

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants