Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upCan't update existing resources with new EBS block device settings #1367
Comments
catsby
added
bug
provider/aws
labels
Apr 2, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Can you post your configuration for that resource? |
phinze
self-assigned this
Apr 2, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
phinze
Apr 2, 2015
Member
Looking into this now. Will try to repro from here, but a config would definitely be helpful!
|
Looking into this now. Will try to repro from here, but a config would definitely be helpful! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
chrisferry
commented
Apr 2, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
phinze
Apr 2, 2015
Member
Reproduced locally with a pretty minimal config.
resource "aws_launch_configuration" "bar" {
name = "dontupdatemebro"
image_id = "ami-21f78e11"
instance_type = "t1.micro"
}Digging in for root issue now.
|
Reproduced locally with a pretty minimal config. resource "aws_launch_configuration" "bar" {
name = "dontupdatemebro"
image_id = "ami-21f78e11"
instance_type = "t1.micro"
}Digging in for root issue now. |
phinze
referenced this issue
Apr 3, 2015
Merged
providers/aws: don't force update for existing launch configs #1371
added a commit
that referenced
this issue
Apr 3, 2015
phinze
referenced this issue
Apr 3, 2015
Merged
helper/schema: ensure ForceNew set when Update is not #1379
added a commit
that referenced
this issue
Apr 3, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
chrisferry
commented
Apr 6, 2015
|
@phinze This fixes the issue. Thx |
phinze
closed this
in
#1371
Apr 6, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chrisferry commentedApr 2, 2015
When running a plan with new 0.4.0 I get the following output:
~ module.inf-consul.aws_launch_configuration.launch_config
ebs_optimized: "" => "0"
ephemeral_block_device.#: "" => ""
root_block_device.#: "" => ""
I'm not specifying a block device in the launch_config.
When I try to apply I receive: