mirror of
https://github.com/opentffoundation/opentf.git
synced 2026-03-20 13:01:28 -04:00
7100a94c26
Unfortunately some existing providers suriously report RequiresReplace paths when they are planning create and/or delete changes, so we'll need to just quietly ignore them rather than generating a user-facing error about it. In practice ignoring these in these cases doesn't really do any harm, since RequiresReplace is only relevant in causing us to reinterpret an "update" into a "replace". But to keep the handling of this quirk centralized, we explicitly throw away spurious paths so that the rest of the system can safely assume that this field will be populated only when some action must be taken based on it. Signed-off-by: Martin Atkins <mart@degeneration.co.uk>