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.

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]: Provider produced inconsistent result after apply when changing the description of a subaccount #278

Closed
1 task done
Lemonron opened this issue Jul 5, 2023 · 1 comment · Fixed by #279
Closed
1 task done
Assignees
Labels
bug Something isn't working

Comments

@Lemonron
Copy link

Lemonron commented Jul 5, 2023

Is there an existing issue for this?

  • I have searched the existing issues

What version of Terraform are you using?

1.5.2

What type of issue are you facing

bug report

Describe the bug

Changing the description of a btp_subaccount from Managed by Terraform! to Managed by Terraform changed! results in the following error when running terraform apply:

btp_subaccount.seoul: Modifying... [id=343cdaeb-215e-47e0-a009-eabbd9dce399]
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to btp_subaccount.seoul, provider "provider[\"registry.terraform.io/sap/btp\"]" produced an unexpected new value: .description: was cty.StringVal("Managed by
│ Terraform changed!"), but now cty.StringVal("Managed by Terraform!").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Expected Behavior

The description should be changed or the provider should report that update is not yet implemented.
Is there documentation on which actions are already supported for which resource type?

Steps To Reproduce

  1. Create a btp_subaccount with a description
  2. Change the value of description
  3. Run terraform apply

Add screenshots to help explain your problem

No response

Additional context

No response

@Lemonron Lemonron added bug Something isn't working needs-triage For new issues labels Jul 5, 2023
@lechnerc77 lechnerc77 removed the needs-triage For new issues label Jul 6, 2023
@lechnerc77 lechnerc77 added this to the 0.2.0-beta1 - July release milestone Jul 6, 2023
@lechnerc77
Copy link
Member

Thanks for bringing this up. Issue is reproducible.

Here sample setup:

provider.tf:

terraform {
  required_providers {
    btp = {
      source  = "sap/btp"
      version = "0.1.0-beta1"
    }
  }
}

# Please checkout documentation on how best to authenticate against SAP BTP
# via the Terraform provider for SAP BTP
provider "btp" {
  globalaccount = "ticrossa"
}

main.tf:

resource "btp_subaccount" "test_subaccount" {
  name        = "My TF Project"
  description = "My TF Project - renamed"
  subdomain   = "my-project"
  region      = "us10"
  labels      = { "Org" : ["my-org"] }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants