-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
WIP: Expose AMI's root volume size #2114
WIP: Expose AMI's root volume size #2114
Conversation
Attempting to implement hashicorp#1623 Right now the tests I've added are failing with the root_volume_size not being set at all. I'll debug this when I get a chance but just want to push the work up for now.
Hmmm... not sure why the Travis build didn't fail last night. Those tests fail locally for me when I run them and building the provider and applying the following config doesn't output the data "aws_ami" "selected" {
most_recent = true
filter {
name = "virtualization-type"
values = ["hvm"]
}
filter {
name = "name"
values = ["amzn-ami-vpc-nat*"]
}
owners = ["amazon"]
}
Adding some debug logging to the data source shows it triggering the if condition at https://github.com/terraform-providers/terraform-provider-aws/pull/2114/files#diff-6c1ccb9926bf208fafaed38fa038b2b4R385 so not sure what I'm missing there. I've got a fair bit on for a couple of days so will probably take a look at it again on Friday/the weekend but I'm confused in both why it's failing locally but also why Travis is passing. |
@tomelliff is this still WIP? |
Any update on this? It would be quite handy ... |
I'd completely forgotten about this to be honest. I can take another look at it if it's useful for others still. |
Closing due to WIP and lack of activity. If you feel like picking it back up, we can certainly reopen this 👍 |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Attempting to implement #1623
The idea is that an instance module should be able to default the root volume to the size of the AMI's root volume. Right now I have a couple of AMIs that have a considerably larger root volume (CUDA/NVidia drivers take a lot of space) and I'd ideally not have to remember to override the root volume size before an apply time failure due to the root volume size being defaulted to a smaller size than the AMI root volume size.
Right now the tests I've added are failing with the root_volume_size not being set at all.
I'll debug this when I get a chance but just want to push the work up for now.
The work here carries on from #1572