-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Can't avoid hardcoding interface:scsi #5295
Can't avoid hardcoding interface:scsi #5295
Comments
@jsoref Is your question is why Terraform is setting SCSI for disk interface?. if so per [https://cloud.google.com/compute/docs/reference/rest/v1/instanceTemplates] (api spec) the default value for disk.interface is Can you please provide a little more detail on what the bug is ? |
@jsoref if you aren't looking for help on this issue, shall i go head and close this one ? |
@venkykuberan: sorry. I thought it was plainly obvious. There's no reason that terraform should take the I'm not sure how else to explain it. Just because Google's backend does something by default doesn't mean your frontend should perform that coercion up front. Let the backend do the conversion. |
Signed-off-by: Modular Magician <[email protected]>
Signed-off-by: Modular Magician <[email protected]>
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
A similarly manually created template doesn't declare a scsi interface -- which to me means that in theory it could change if google updates their defaults (which is perhaps something i might want):
Actual Behavior
plan output:
describe output:
Steps to Reproduce
terraform apply
gcloud compute instance-templates describe node-native
gcloud compute instance-templates describe node
gcloud compute instance-templates describe node-scsi
Important Factoids
I have pre-existing manually created templates that I kind of like. I'd like to migrate to using terraform w/o losing their characteristics.
(Yes, I understand SCSI is the default today, and the terraform behavior is documented, but it clearly isn't required from gcloud's perspective.)
References
This is in the family of #5283 -- things which do not quite work the way I'd like in that I can't produce the output I'd like the way I'd like / there doesn't appear to be any way to do so using terraform.
b/308756461
The text was updated successfully, but these errors were encountered: