Ian Arsenault comments

Repositories
Issues
Comments

Results 2 comments of


                                            Ian Arsenault

Next Button Problem

#7 I believe this might be the same issue.

the provider continues to reveal sensitive variables during destroy or update in-place

A potential _hacky_ workaround to this is to add metadata to lifecycle ignore_changes, however this will spit out a warning indicating it's decided by the provider and not an argument...