Add documentation for outside release usage

[fisehara]

The fin block image can be used outside of a fleet release.
For example for ad hoc or sporadic usage on FIN devices.

[ghost]

Your landr site preview has been successfully deployed to https://landr-balenablocks-repo-fin-preview-55.netlify.app

Deployed with Landr 6.36.2

[Bucknalla]

@fisehara currently we use balenacloud to apply tags as well as do some other things, I'm not sure this will work without a fleet right now?

[fisehara]

@Bucknalla I see. I wanted to highlight that the block can be used outside of a release. To retrieve ad hoc information from a FIN that is already in production and deployed to the field.
Do you think I should just refine it in the doc or would you keep this out of this repo at all?

[Bucknalla]

@fisehara I'd really like to re-write the block such that it can be used completely independent of balenaCloud. So perhaps that's the direction we move towards, where certain functionality is disabled if not using balenaCloud?

If you're thinking of using this as a utility tool, for example for support tickets, I think that also has merit but I think I would like package in a more user-friendly mechanism. I will be breaking the node modules into standalone packages at some point so this might make more sense when you can use them as node modules.

[fisehara]

@Bucknalla In my case it was a user request having a FIN fleet and wanting to check which HW revision each device has. For this I liked the approach of just pulling an image. An image came very useful as it could be executed directly by the balena engine without installing, setting up or anything. Thus an image that has only the ad hoc functionality and the full features when deployed in a balena release would make sense.

I think splitting it down makes sense, but maybe ends up in a more complicated 'putting all modules together'. When having node modules that a user would have to put into a docker image and push to a registry that is accessible by a device it becomes more a development task than a tool.

[fisehara]

@Bucknalla as it's just an addtional documentation for the fin block, do you see any blocker on just merging it?

[fisehara]

dropping it for inactivity