MAAS2: handle fields that might be missing or null from the API #54

Merged
merged 4 commits into from May 3, 2016

Conversation

Projects
None yet
3 participants
Member

babbageclunk commented May 3, 2016

I asked the MAAS team to look through a list of all the fields that we're using in the MAAS v2 API and tell us which of them were optional or nullable. These changes are based on the information they gave us back.

Based on the spreadsheet here: https://docs.google.com/a/canonical.com/spreadsheets/d/1qysFkvJwz3w19B3kYcnlokwqdTb82HGCrF4pUk6gtfA/edit?usp=sharing

Contributor

dimitern commented May 3, 2016

LGTM

Member

babbageclunk commented May 3, 2016

$$merge$$

Contributor

jujubot commented May 3, 2016

@jujubot jujubot merged commit 5bd7212 into juju:master May 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment