Open ryancrawcour opened 3 months ago
Hey, thanks for reporting this! Just to check I understand correctly, it's removing the sub-projects at any subsequent apply after the top level project is provisioned? Or during any specific tf actions? Generally TF is setup to just ignore things it doesn't know about/ "own", so this feels weird, good catch!
When using this provider, i can setup a project, and sub-projects, etc. great.
However, i want to let users create additional sub-projects under the root-level project i provision for each team.
If a user adds the project directly in the Tableau UX that the state file doesn't know about Tf tries to remove the project, as it should, as is typical of Tf.
Is there a way to get the provider to ignore things it doesn't know about, rather than delete them? Is there a way to get the provider to only care about projects up to a specified level? i.e. care about the Tableau root level projects, and any child projects, but then not care about any children to the root-level children?
tableau -- main -- -- finance -- -- -- some folder -- -- -- some other folder -- -- marketing -- -- sales
in this example, have Tf care about main, finance, marketing and sales, but ignore the fact that there are these "other folders" under finance.