Closed AndriiPysmenko closed 1 year ago
Thank you for reporting this issue, I'll take care of fixing this quickly.
@jeremmfr thank you for your work on this. I was working more the the provider and found the state was never migrated and I still needed to do a state remove and import. for it to work. I at first attributed it to perhaps the state thinking I already upgraded to version 2 of this provider (Since I could not rollback to 1.33). When I got to look closer, I wonder if we would need to version the schema as mentioned here to trigger the migration: https://developer.hashicorp.com/terraform/plugin/framework/resources/state-upgrade#stateupgrader-with-priorschema
I could not find a mention of the version field in: https://github.com/jeremmfr/terraform-provider-junos/blob/8c4784690dbd35961e3447dab8fb78d375eb39c9/internal/providerfwk/upgradestate_forwardingoptions_sampling_instance.go
This is a new aspect of Terraform shema to me that I havent gotten to consider in my work with programming go Terraform. Do you think that may be what I am hitting?
@jeremmfr thank you for your work on this. I was working more the the provider and found the state was never migrated and I still needed to do a state remove and import. for it to work. I at first attributed it to perhaps the state thinking I already upgraded to version 2 of this provider (Since I could not rollback to 1.33). When I got to look closer, I wonder if we would need to version the schema as mentioned here to trigger the migration: https://developer.hashicorp.com/terraform/plugin/framework/resources/state-upgrade#stateupgrader-with-priorschema
I could not find a mention of the version field in: https://github.com/jeremmfr/terraform-provider-junos/blob/8c4784690dbd35961e3447dab8fb78d375eb39c9/internal/providerfwk/upgradestate_forwardingoptions_sampling_instance.go
This is a new aspect of Terraform shema to me that I havent gotten to consider in my work with programming go Terraform. Do you think that may be what I am hitting?
@computeracer I think your comment concerns issue #536 and not this one.
If you have already updated the provider, the resource state has already upgraded to new version 1
(instead of 0
). In this case, you need to launch the command terraform plan
or terraform apply
without -refresh=false
or command terraform apply -refresh-only
to update the value of routing_instance
to the default default
.
Hi,
After upgrade terraform provider to version 2.1.0 resource junos_policyoptions_policy_statement starts to work incorrect.
Terraform and Provider Versions
Terraform Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Additional Context
References