fix: use reportTypeId for equality check and some null checks #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
When checking for existing youtube reporting jobs, the tap uses the
job.name
to check if it exists in the stream butjob.name
is user specified and could be different from what's expected. Specifically in cases where the job wasn't created by the tap. The fix is to use thejob.reportTypeId
which is consistent across, ensuring we don't try to create an existing job which throws a 409 error and breaks the tap.Other changes are just some null checks that break the tap.