forked from hashicorp/terraform
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Rebasing from master and including fix for encrypted ebs #14
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit patches a few acceptance tests in order to get them to pass under OpenStack Mitaka. The devstack dev environment script has also been updated to reflect OpenStack Mitaka as well as the new Terraform dependency vendoring.
…rraform into f-cloustack-group
provider/cloudstack: add group attribute for instance resource
…icorp#6186) The flattening process was not properly drawing dependencies between provider nodes in modules and their parent provider nodes. Fixes hashicorp#2832 Fixes hashicorp#4443 Fixes hashicorp#4865
hil.Eval() now returns (hil.EvaluationResult, error) instead of (value, type, error). This commit updates the call sites, but retains all previous behaviour. Tests are also updated.
deps: Update hil and call sites of hil.Eval
This strips debug information from the binaries, making them slightly smaller.
…nstalk_environment resource. (hashicorp#6167) Fixes hashicorp#6164.
Fix hashicorp#3562 provider/vsphere Added doc for customizations problems.
…stomization provider/vsphere: Add setting to skip customization
Allow running tests when AWS_PROFILE is set, needed for STS users
provider/triton: Add NICs to triton_machine resources
This allows the acceptance tests for librato to pass.
Fixing the broken Test with Master branch
If any of the entries in `commands` on `docker_container` resources was empty, the assertion to string panic'd. Since we can't use ValidateFunc on list elements, we can only really check this at apply time. If any value is nil (resolves to empty string during conversion), we fail with an error prior to creating the container. Fixes hashicorp#6409.
…nd-crash provider/docker: don't crash with empty commands
Track enhanced links
* Adding File Resource for vSphere provider Allows for file upload to vSphere at specified location. This also includes update for moving or renaming of file resources. * Ensuring required parameters are provided
…icorp#6442) * provider/aws: Improve error handling in IAM Server Certificates * rename test, add additional empty check
Shipit
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.