6cc0a7d887
So far, using YAMLAdapter in pools.yaml context, without providing all of the pools.yaml attributes altogether, failed because of YAMLAdapter. An example could be an end user who wouldn't like to deploy catalog zones in its pools and therefore would drop that attribute from the pools.yaml file, like in designate/tests/resources/pools_yaml/multiple-pools.yaml. Running any designate-manage pool command on a file without all of the pools.yaml attributes will fail with the following error message: designate.exceptions.AdapterNotFound: Adapter for None to format YAML not found This patch fixes it. Closes-Bug: #2064720 Change-Id: I214cfc05a834d97a61d0236ab223470631bfc405
7 lines
231 B
YAML
7 lines
231 B
YAML
---
|
|
fixes:
|
|
- |
|
|
So far, the yaml Adapter made every designate-manage pool command
|
|
fail if the pools.yaml file was missing any of the pool attributes.
|
|
This patch makes the adapter to continue without raising any error.
|