[Bug]: Volume attachment "config_id" is missing, may cause Volume resource creation to fail if Instance has multiple config

[PierreBeucher]

I'm trying to create a linode_volume for an Instance with multiple linode_instance_config, but it fails with error such as:

  linode:index:Volume (test-instance-xxx):
    error: Failed to Attach Volume 123456 to Linode 123456: [400] [config_id] Couldn't choose a configuration profile to add this volume to. Please add this volume to the configuration profile you want.

This happens when instance has never been booted, eg. using booted = false. When instance has been booted at least once, volume is attached on latest used instance_config which prevent user from choosing the instance_config on which volume is finally attached.

instance_config parameter is mentioned on Volume attachment API but there's no input on linode_volume resource. Is it possible to add it?

Note: issue originally created on Pulumi provider based on this one

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[PierreBeucher]

Not stale.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[PierreBeucher]

Not stale. @zliang-akamai sorry to ping you directly but you seem knowledgeable about this issue. Can you take a look? Thanks!

[zliang-akamai]

Hi @PierreBeucher, thanks for bringing this issue to my attention! Would you be able to provide a Terraform or Pulumi config code snippet that reproduces this issue?

[PierreBeucher]

Will do !