Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle cases of bad parent/child modelling #130

Open
alex-frankel opened this issue Sep 25, 2020 · 2 comments
Open

Handle cases of bad parent/child modelling #130

alex-frankel opened this issue Sep 25, 2020 · 2 comments

Comments

@alex-frankel
Copy link
Contributor

Cases where a resource (i.e. subnets) is modelled as both a child resource and as a property of the parent resource. This effectively tricks what-if into thinking the resource exists/could exist in both places because the VNET will return subnet info in it's GET response AND we can GET the resource directly as a child resource.

@ghost ghost added the Needs Triage 🔍 label Sep 25, 2020
@alex-frankel
Copy link
Contributor Author

@alex-frankel alex-frankel pinned this issue Sep 25, 2020
@alex-frankel alex-frankel changed the title Bad parent/child modelling Handle cases of bad parent/child modelling Sep 25, 2020
@shenglol
Copy link
Collaborator

#140

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants