Hey guys, I have been going over this component https://docs.cloudposse.com/components/library/aws/eks/karpenter-node-pool/#option-2-using-atmos-terraformstate-recommended it mentions to use the

Option 2 Using Atmos !terraform.state

which is recommended way, is there any specific reason not to use remote-state as recommended way, I see that the remote-state way will be deprecated in newest release. Did you guys experience some issues with remote-state and or just decided to move away from remote-state entirely for all the other components as well?

We want to eliminate the reliance on remote state inside of our components (e.g. using data sources that query account map) so that they work better in brown field environments. That makes the components more reusable while still being able to use remote state when passing configuration from atmos