Skip to content

Error during update - Provider produced inconsistent result after apply #355

Description

@maheshwarishikha

With version 3.0.0 -

If we update the existing infra, then most of the time it gives error as:

Error: Provider produced inconsistent result after apply

Observed this behavior with multiple APIs that shows it is independent of API.

Some of the error with GitHub APIs are here for your reference:

 Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to restapi_object.repository_crud, provider "provider[\"registry.terraform.io/mastercard/restapi\"]" produced an unexpected new
│ value: .api_data["description"]: was cty.StringVal("Initial description - created via POST"), but now cty.StringVal("Updated description - created via
│ POST").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to restapi_object.repository_crud, provider "provider[\"registry.terraform.io/mastercard/restapi\"]" produced an unexpected new
│ value: .api_data: element "temp_clone_token" has vanished.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to restapi_object.repository_crud, provider "provider[\"registry.terraform.io/mastercard/restapi\"]" produced an unexpected new
│ value: .api_data["updated_at"]: was cty.StringVal("2026-03-27T02:06:10Z"), but now cty.StringVal("2026-03-27T02:09:23Z").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵

In-spite of this error, actual changes takes place i.e infra is updated and next plan shows:

No changes. Your infrastructure matches the configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions