Accessing nested values in import is non-ideal: fix option 1

[icanhazpython]

Fix option 1 for #2474

[cla-bot]

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @icanhazpython

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.

• If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.

[icanhazpython]

CLA signed

[bobapple]

@cla-bot check

[Thomas-Gelf]

Thank you for your pull request! I didn't merge this, as IMHO it SHOULD fail in case of conflicting types, like app being a string or an array (instead of an object) when accessing app.name:

• { "app": null }: should shipnull
• { "no app": "something" }: should ship null
• { "app": "a string" }: should fail
• { "app": false }: should fail
• { "app": { "name": "app" }: should ship "app"

I'll push a related fix.