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.

Sign up for GitHub

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

Jump to bottom

Make the OpsWorks cookbooks SSH key write only #4241

Merged
merged 1 commit into from
Dec 10, 2015
Merged

Make the OpsWorks cookbooks SSH key write only #4241

merged 1 commit into from
Dec 10, 2015

Commits on Dec 9, 2015

  1. Make the OpsWorks cookbooks SSH key write only 

    Fixes hashicorp#3635

This follows the suggestion of @apparentlymart in
hashicorp#3635 (comment)
to fix the issue of OpsWorks stacks always complaining about the custom
cookbooks SSH key needing to be changed.

Functional tests:

* Created a new stack and gave it an SSH key. The key was written to
  OpsWorks properly.
* Ran "plan" again and terraform indicated it needed to change the SSH
  key, which is expected since terraform cannot read what the existing
  SSH is.
* Removed the key from my resource and this time, "plan" did not have
  any changes. The `tfstate` file indicated the SSH key was "" (empty
  string).
* Changed an unrelated property of the stack. Previously this was not
  working for me due to terraform attempting to change the SSH key.
    @b-ryan
    b-ryan committed Dec 9, 2015
    Configuration menu
    Copy the full SHA
    921944c View commit details
    Browse the repository at this point in the history