-
Notifications
You must be signed in to change notification settings - Fork 428
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 Crash when applying masking policies #3331
Comments
Hey @AaronCoquet-Easypark. Thanks for reaching out to us. Can you please share the logs from the crash? The provided logs above show only the plan output and not the result of the |
Turns out the whole logs were large enough that GitHub rejected them! |
Logs look good now, thanks. The issue is that in The panic is not ideal here, and an error should be returned instead. We plan to rework tables and the associations soon, so this will be fixed. |
That seems to have mostly fixed it! However, it raises a different issue: when I use
|
I'm sorry, I did not verify this properly. The diff suppressor in the preview resources is sometimes not correct. Still, you need to use fully qualified names here, but with a matching format, so please use the TF function This permadiff shouldn't occur, and during the rework, we will fix this. |
As a fix, I set my DB, Schema, Table, and Column names to be quoted if they aren't all caps: format("%s.%s.%s",
database == upper(database) ? database : format("\"%s\"", database),
... schema ...,
... table ...
) |
Terraform CLI Version
1.9.8
Terraform Provider Version
1.0.1
Company Name
Easypark
Terraform Configuration
Category
category:resource
Object type(s)
resource:masking_policy
Expected Behavior
Actual Behavior
Steps to Reproduce
example.json
local
to look at the JSON fileHow much impact is this issue causing?
Medium
Logs
https://gist.github.com/AaronCoquet-Easypark/d9367f5ce67ad0b246b3b103f0088a51
Additional Information
Some, but not all, of the masking policies were created. None of the masking policies were applied.
Would you like to implement a fix?
The text was updated successfully, but these errors were encountered: