Resources receiving their configs from another directory are blocked with --restrict-file-list parameter

[ibalat]

Hi @Fabianoshz , thanks for your contribute (#2440), this feature is very important for our monolithic repos security. But we have an failed scenario for this feature:

I have an resource getting configs from subfolder and when I change any config, I can't run atlantis command because of changes at subfolder.

My resource location: clusters/dev/main.tf
Config location: clusters/dev/configs/dashboards/application
I have to apply resource in main.tf

my resource is getting configs from another location:

grafana_dashboard_kubernetes = {
    for dashboard in fileset("${path.module}/configs/dashboards/application/", "*.json") :
    dashboard => file("${path.module}/grafana/configs/application/${dashboard}")
  }

Can we add recursive check? Or another parameter is available to fix it?

[Fabianoshz]

Hi @ibalat, I'm not an active contributor anymore as I'm not using Atlantis anymore.

Looking at the code it seems to be easy to fix though, so I might give it a shot if I manage to find some time.

[ibalat]

@Fabianoshz thanks for your fastly reply. I have opened a PR. Please can you review it? #4972