Skip to content

The provider always changes the account for ytsaurus_map_node, even if the account has not been changed and is not included in the plan #9

@sasorokinnebius

Description

@sasorokinnebius

The provider always changes the account for ytsaurus_map_node, even if the account has not been changed and is not included in the plan.
It leads to unnecessary lock of the ytsaurus_map_node.

  ~ update in-place

Terraform will perform the following actions:

  # module.***.ytsaurus_map_node.**** will be updated in-place
  THERE IS NO ACCOUNT CHANGE
  ~ resource "ytsaurus_map_node" "*****" {
      ~ acl         = [
          ~ {
              ~ subjects         = [
                  + "some_subjet",
                    # (21 unchanged elements hidden)
                ]
                # (3 unchanged attributes hidden)
            },
        ]
      ~ id          = "some id" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

module.some_module: Modifying... [id=some id]
╷
│ Error: Error updating map_node attributes
THE ACCOUNT OF THE TABLE ALREADY some_account
│ Could not set node "#some_id/@account" to
│ 'some_account', unexpected error: "call

Metadata

Metadata

Assignees

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