Bugfix/missing schema columns

[awoehrl]

@bcodell, I found a bug in my codegen macro.

I missed that the schema_columns macro doesn't contain the anonymous_customer_id column. Also I realized, I was using customer_id, when the activity schema specs use customer for the customer column.

Right now this means, that customer and anonymous_customer_id won't get renamed correctly if aliased.

My further question would be:

• Would it make sense to have a global macro that delivers all columns, aliases and a flag if the field is used for an activity?

[bcodell]

Would it make sense to have a global macro that delivers all columns, aliases and a flag if the field is used for an activity?

Hey @awoehrl this is a great callout! As part of my work to provide support for anonymous_customer_id, I'm going to update the schema_columns macro to accept an optional argument for stream. If passed, then the macro will return a dictionary that contains the appropriate metadata for the customer and anonymous_customer_id columns. I'll follow up here once that's merged so you can put it to use in the code generation macro. Thanks!

[bcodell]

Hey @awoehrl the schema_columns now accepts an optional stream argument, which will prompt the macro to return appropriate metadata for all columns. Give it a go in this PR!

[bcodell]

Hey @awoehrl - thanks for the updates! And I appreciate you adding a model to use for testing 🙏 Looks like these changes broke CI though. I'm going to pull down to my local machine to see if this issue is related to CI running on a forked branch. If that's the case, then we should be good to merge! If not, given that this is a utility function, I'd be okay with deprecating the testing and just shipping the changes to the macro.

[bcodell]

Better (very) late than never... confirming the failed CI is related to secrets access. Sorry for leaving this hanging @awoehrl and thanks for contributing!