You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 27, 2021. It is now read-only.
Terraform seems to be asserting hashes of the content and the API response because it will constantly complain about whitespace and recommend updating the resource:
Terraform will perform the following actions:
# gsuite_user_attributes.test will be updated in-place
~ resource "gsuite_user_attributes" "tonys_permit" {
id = "111111111111111111111"
primary_email = "[email protected]"
~ custom_schema {
name = "PERMIT"
~ value = jsonencode( # whitespace changes
{
Role = [
{
type = "work"
value = "aaa"
},
{
type = "work"
value = "bbb"
},
]
SessionDuration = "ccc"
}
)
}
}
Plan: 0 to add, 1 to change, 0 to destroy.
I was able to workaround that issue by updating my resource:
Not sure whether it's something that might or even needed to be fixed on a provider level, so feel free to close this issue.
In any case, this is something that might be useful to be noted in the documentation, and of course, this issue here might help others to solve a similar problem 😉
The text was updated successfully, but these errors were encountered:
Hello @DeviaVir,
First of all, thanks for a great provider here! 👑
I have encountered an issue deploying a resource with a JSON string.
The problem arises when a string is provided in a formatted way, like this:
Terraform seems to be asserting hashes of the content and the API response because it will constantly complain about whitespace and recommend updating the resource:
I was able to workaround that issue by updating my resource:
But a more suitable solution was ofcourse using the
jsonencode
:Not sure whether it's something that might or even needed to be fixed on a provider level, so feel free to close this issue.
In any case, this is something that might be useful to be noted in the documentation, and of course, this issue here might help others to solve a similar problem 😉
The text was updated successfully, but these errors were encountered: