It does indeed raise a few questions, would you even be interested in having a zone named default if you use the configuration option? It would also be problematic to handle any changes to the config post-deploy.
FWIW, if a immutable config type approach would be on the table we have an example of how that can be handled here: https://review.opendev.org/#/c/701476/
It does indeed raise a few questions, would you even be interested in having a zone named default if you use the configuration option? It would also be problematic to handle any changes to the config post-deploy.
FWIW, if a immutable config type approach would be on the table we have an example of how that can be handled here: https:/ /review. opendev. org/#/c/ 701476/