Bug 1810209

Description of problem: Since adding the validation check that prevents customers from messing up deployments by forgetting to include network-isolation or network-environment files  [1] , we are now unable to delete an overcloud network. For example if we deploy with Management or some other network and later need to delete it since it's not used we can not. This validation will notice heat stacks for that network and double check that it is defined in the templates. So if you just remove the network from the templates in hopes the network gets deleted, the deploy fails because of this validation. There was a similar bugzilla where this issue was hit here [2] . Maybe  NetworkDeploymentActions: ['DELETE', 'UPDATE'] would allow the ability to delete overcloud networks ?

[1] https://github.com/openstack/python-tripleoclient/blob/84c7226b2782f3085660171506112cfe7c0dc2dd/tripleoclient/utils.py#L582

[2] https://bugzilla.redhat.com/show_bug.cgi?id=1764470


Version-Release number of selected component (if applicable):
OSP13

How reproducible:
100%

Steps to Reproduce:
1. steps in bug [2]
2.
3.

Actual results:
unable to deploy if an overcloud network exists but is removed from templates

Expected results:
Ability to disable validations so networks can be removed from templates and then deleted from the overcloud environment.