Issue with Stream Entity, Things with scheduler as base

[thomas-thomas-tfs]

• [ ] Data Shapes extended with streams are not getting added to resultant Stream
• [ ] How to provide @schedule and run as params for things to be created from Scheduler Thing

[BogdanMihaiciuc]

Hey, can you clarify the first issue, I'm not sure I understand what is wrong. If it's unrelated to the second point please open a separate issue for it.

For the second one, there is currently no way to specify property and configuration values (other than defaults) to be used when importing; Scheduler and Timer configurations are such runtime values. While these can't be specified through typescript, they will be retained through updates in Thingworx if you set them once.

I've been looking for a way to include property values and configurations in the generated export files, but I haven't found a way that I'm happy with yet.

[carlo-quinonez]

What have you considered for setting configurations and property values? Some of these are per-environment in our case, and I'd love to be able to inject the appropriate per-env values at build time.

[BogdanMihaiciuc]

I was considering having a separate file, like a json or env file, that would contain these runtime values.

I'm open to suggestions on how to best handle this use case.

It's technically easy to do, since these values can be specified in the generated xml, but I haven't yet found an approach I'm happy with.