-
Notifications
You must be signed in to change notification settings - Fork 17
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
[BUG] btp_subaccount_service_instance: "AttributeName("context"): unsupported type json.Delim sent as tftypes.String" after upgrading rc1 -> rc2 #674
Comments
@SeanKilleen : The issue you are facing is due to the breaking change we had to introduce in the RC2 as some backend API made incompatible schema changes of the response object. This is mentioned in the release notes and the linked PR #609 As we are not GA yet we do not provide migration options or implement the state-upgrade function. After GA situations like this will be avoided or if we are forced to do it, handled on our end. In order to overcome this issue for now, you can give the
|
@lechnerc77 ahhh, sorry for missing that in the release notes; I forgot that I was using that resource and I skimmed way too quickly. As you predicted, Is this something that will break from me from this point onward? Or something that will be resolved when things go GA? Trying to understand my path forward. |
@lechnerc77 FWIW when I attempt to taint the resource, I see an error:
Is that related to this as well? I'd expect to be able to taint something still. |
@SeanKilleen concerning the way forward: there are no breaking changes to expect from RC2 to GA release, at least as of today we do not have any breaking change in our backlog. Of course, I cannot exclude the possibility if a bug is that leads to such a change, that this might happen, but chances of another breaking change are low. From GA onwards we will take care that breaking changes will be avoided or properly mitigated so that there is no disruption on your end. With respect to the |
@lechnerc77 My question was: there's not going to be some upgrade resource added to solve this in GA from where I am now, right? I'm trying to understand my options. It sounds like no matter what my only option is to delete this resource to recreate it, since taint also isn't working. And regardless of any future releases, this will be a step I need to take. Correct? |
I understand. So from my perspective you have two options: Option 1 is as you write deleting the resource and recreating it. However, there might be side effects depending on your overall configuration. This is something I cannot make any comment on. Option 2: You try to manually correct the state file be changing the content of the |
Thanks! I'll take a backup of my state and try the manual update tomorrow. I'll let you know the results. |
@lechnerc77 This worked! Took the following steps in case anyone else is wondering.
At this point it actually failed with an error Once that was complete, terraform apply worked as expected. Just need to perform that step for each environment and I'll be good to go. Thanks for the guidance! |
@SeanKilleen Great to hear that it worked. Sorry for the inconveniences that you had. As mentioned once we go GA hiccups like this will be avoided from our end as far as possible. |
@lechnerc77 no problem! Being part of the road to production is bound to have these bumps. Your great guidance has made all the difference. |
This worked like a charm! Thanks for sharing. |
Is there an existing issue for this?
What version of the Terraform provider are you using?
1.0.0-rc2
What version of the Terraform CLI are you using?
1.7.0
What type of issue are you facing
bug report
Describe the bug
I've got a service instance that has been in place for a while long time:
I upgraded from 1.0.0-rc1 to 1.0.0-rc2 of the provider.
After doing so, when applying the TF, I see:
This was done in a branch where the only change was to upgrade the provider.
Downgrading back to 1.0.0-rc1 removes the issue.
Expected Behavior
Since my Terraform has not changed and my environment has not changed, I'd expect to see that there are no changes.
Steps To Reproduce
No response
User's Role Collections
No response
Add screenshots to help explain your problem
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: