Bug Report: `Core.IncludeResourcesInResourceGroup` setting not working as expected

[matthewponzio]

Describe the bug
I have the following configuration in my settings.json

"Core.IncludeResourcesInResourceGroup": ["cloud-eng-network"],

I would expect that the Pull pipeline would then ONLY discover Resources in Resource Groups named cloud-eng-network

However, when I add Resources to Resource Groups OTHER THAN cloud-eng-network, they are still being discovered.

Steps to reproduce

1. Create a Resource Group named cloud-eng-network
2. Create a Resource Group named <your_choice>
3. Configure "Core.IncludeResourcesInResourceGroup": ["cloud-eng-network"], in settings.json
4. Add any Resource to each of the two Resource Groups
5. Run the Pull pipeline
6. Notice that BOTH Resources are discovered -- instead of ONLY the Resource within the cloud-eng-network Resource Group

Screenshots

[daltondhcp]

Thank you for raising this. Maybe I wasn’t very clear around this in the question you asked under discussions. That feature is introduced in #609, but we haven’t cut a release for it yet. Targeting for 1.8.0 in a week or so.

Apologies for the inconvenience.

[matthewponzio]

@daltondhcp Oh my...of course..derp. I spent a bunch of time reading through the code to see if maybe I was misunderstanding the intent of the feature..and I'm like yeah, it looks like it's all set up to work like I understood?! But then...I'm looking at my cloned copy of master ...and not 1.7.7. Ugh. 🙄 I didn't actually think it was a bug, but it seemed more appropriate to bring it up there than in Discussions. Anyway, thanks again for the reply. You definitely saved me some additional head scratching today!

[daltondhcp]

Any time, looking forward to your feedback when we have shipped it! 😄