feature(is_instance): resize boot volume

[ujjwal-ibm]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #2205

Output from acceptance testing:

--- PASS: TestAccIBMISInstance_ResizeBoot (269.09s)
PASS
ok  	github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/vpc	271.042s

--- PASS: TestAccIBMISInstance_basicwithipv4 (195.62s)
PASS
ok      github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/vpc     691.706s

--- PASS: TestAccIBMISInstanceSnapshotRestore_basic (580.66s)
PASS
ok      github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/vpc     582.528s

--- PASS: TestAccIBMISInstanceBandwidth_basic (296.80s)
PASS
ok      github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/vpc     298.455s

--- PASS: TestAccIBMISInstance_action (458.99s)
PASS
ok      github.com/IBM-Cloud/terraform-provider-ibm/ibm/service/vpc     460.413s

[astha-jain]

Looks good. @hkantare Please take a look.

[hkantare]

@ujjwal-ibm PR looks fine but can we test one scenario
Provision the resource using old binary 1.39.1 something and then use the new binary and compare the plan . It should n't have any diff

[ujjwal-ibm]

@hkantare
tested the scenario, it shows no change, just an addition of computed volume_id attribute

      ~ boot_volume {
            name       = "divot-track-majority-trespass"
          + volume_id  = "r010--aa51-408e-8b20-9ad0912a3a62"
            # (4 unchanged attributes hidden)
        }


No changes. Your infrastructure matches the configuration.