Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ibm_resource_instance forces a replacement on updates to parameters field #1705

Closed
ashishth09 opened this issue Jul 18, 2020 · 3 comments
Closed

ibm_resource_instance forces a replacement on updates to parameters field #1705

ashishth09 opened this issue Jul 18, 2020 · 3 comments

Comments

@ashishth09
Copy link
Collaborator

https://github.com/IBM-Cloud/terraform-provider-ibm/blob/master/ibm/resource_ibm_resource_instance.go#L88.
I can very well update the memory, endpoints type etc. Why is it restricted?
@ashishth09 ashishth09 reopened this Jul 18, 2020
@ashishth09
Copy link
Collaborator Author

I can see it has https://github.com/IBM-Cloud/terraform-provider-ibm/blob/master/ibm/resource_ibm_resource_instance.go#L403 function which can do the updates in-place so why destroy and create

@AnandPalani92
Copy link

Hi Team,

When i can expect this fix in IBM terraform provider plugin.

We need it soon and update the IBM resources on environment.

hkantare added a commit to hkantare/terraform-provider-ibm that referenced this issue Sep 22, 2020
@hkantare
Support update of parameters for resource instance IBM-Cloud#1705
6b3ce31
hkantare added a commit that referenced this issue Sep 25, 2020
@hkantare
Support update of parameters for resource instance #1705
0b550dc
@hkantare
Copy link
Collaborator

hkantare commented Oct 7, 2020

Fixed in latest release
https://github.com/IBM-Cloud/terraform-provider-ibm/releases/tag/v1.13.0

@hkantare hkantare closed this as completed Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ashishth09 @AnandPalani92 @hkantare