-
Notifications
You must be signed in to change notification settings - Fork 143
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
Move non-core DNS zones outside network module #3119
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/4006311780 (with refid (in response to this comment from @tamirkamara) |
ca82037
to
0e9ccad
Compare
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/4007014871 (with refid (in response to this comment from @tamirkamara) |
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/4007605820 (with refid (in response to this comment from @tamirkamara) |
19fc119
to
4ee5c7f
Compare
/test |
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/4013194654 (with refid (in response to this comment from @tamirkamara) |
What is being addressed
We create many objects in the network module that cause delays on its completion but aren't really required to be provisioned there.
How is this addressed