Closed jonnagel closed 3 years ago
CRITICAL 'metadata'
Looks like a KeyError
, but you trimmed the rest of the stack trace
updated the post
So we expect _get_fields to_return[extension_id]
to be a dict
that has a key metadata
, but it doesn't.
Is that allowed?
I'm just an end-user, I'm not sure what is allowed. Should the discovery process extract metadata? Are there additional permissions needed for this that are not needed for other steps?
I don't know how debugging with anacoda works, but if you are able to edit the tap, run it, and see your changes take effect then I would do the following:
LOGGER.info("to_return for %s: %s", extension_id, to_return)
INFO: to_return
The rest of that line - it might be very verbose - should look something like this. I expect it to be missing that 'metadata'
key though since that's what your error is.
This line and this line make me think that extention_id
and customer_id
are supposed to be the same thing, but I don't know what those are, so I can't say for sure.
This is all of the insight I have for you, good luck
"batch_size": 5000
Seems to have made this work in my case.
I think I have collected everything needed, please let me know if more information is needed.
OS: Ubuntu 20.04.1 LTS Pull from master, build, edit config.json (all done today)
Run: tap-exacttarget -c config.json --discover > catalog.json
[trimmed]
[trimmed]