Nick Nikitas

Take a look at this issue https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/1082 and at this discussion https://github.com/Snowflake-Labs/terraform-provider-snowflake/discussions/740 which mention the same problem, yet no solution is provided.

We can let the maintainers decide :)

I have the same issue as @lp-code. There are no user/role grants imported although the import command runs without errors(provider version 0.39.0). Any solutions/suggestions?

@blackpiglet Hello, Regarding the resource-modifer CM: ``` apiVersion: v1 data: resourcemodifierrule.yaml: | version: v1 resourceModifierRules: - conditions: groupResource: persistentvolumeclaims resourceNameRegex: "ebs-mongo-claim" namespaces: - test-namespace patches: - operation: replace path: "/spec/storageClassName"...

@blackpiglet No namespace is backed-up and no namespace is deleted. I only backup the PV/PVC in a specific namespace.

I also faced this yesterday. In order to overcome this without modifying the Hudi source code, I used the `SqlQueryBasedTransformer` and the `ComplexKeyGenerator` to extract the `year`,`month` and `day` values...

Yes they can be implemented through the aws-api-mcp-server, i guess that we can close the PR!

Yes they can be implemented through the aws-api-mcp-server, i guess that we can close the PR!