-
Notifications
You must be signed in to change notification settings - Fork 121
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
awscc_redshiftserverless_namespace - "NotUpdatableException: β Invalid patch update: createOnlyProperties [/properties/Tags] cannot be updated" #1928
Comments
Thank you for opening the issue @hszalwinski .I can reproduce it and it does look like the ordering on the log_exports leading to a drift. Adding some additional details for further debugging. Debug log
PlanResourceChange_Request_PriorState
PlanResourceChange_Request_ProposedNewState
PlanResourceChange_Response_PlannedState
|
From the schema, insertionorder shouldn't be a factor.
Statefile has
|
The get-resource response ( on refresh or subsequent plan/apply) shows the ordered list and hence provider is showing a drift.
translates to ..
|
This needs some review as Tags on namespace is an replace operation for the resource from the schema and it would fail with a resource with a custom name. Opened an internal service ticket to review the schema around |
The secondary issue on the tags being added in the patch operation when anything changes needs to be reviewed. |
Hello! Any news or fix time estimations @quixoticmonk? :) |
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Terraform v1.9.3 on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Docs state, that
log_exports
should be aList of String
. I would expect either the documentation to be fixed or implementation to handle the bug case.Additionally and even more important, it is not only an issue with
log_exports
. When I try to update existing resource by e.g. changing theadmin_password_secret_kms_key_id
or adding another role toiam_roles
. I receive the same error from Cloud Control API. I expect the issue not to appear, so noin-place updates
should be blocked by this.Actual Behavior and Steps to Reproduce
awscc_redshiftserverless_namespace
providinglog_exports
as alist
theterraform apply
command succeeds (1st gist).No changes.
output like in 3rd gist. Instead of this, I receive an error (2nd gist):log_exports
fromlist
to aset
and runterraform apply
once again it produces desired output. I've also checked, that it works okay if I useset
from the beginning.The text was updated successfully, but these errors were encountered: