Is there anyway to deploy flows to multiple devices and not have the credentials for applicable nodes not lose configuration?
I tried deploying the flows credential file when I deployed the matching flows file. But I still get the warning that the credentials file is invalid, which is understandable, if I understand the design as such, anchored to the original system instance, if not node red instance.
If there is not a way to do such, I would point out that cached (once validated) credentials are deployed remotely all the time, in various environments and for various solutions. If the given id does not exist on the remote machine, or the password is out sync, failure results, which is the correct behavior, so it would not be like you could somehow establish or create access from accepting deployment of cached credentials.
There really should be some option for this IMHO. How about the warning dialog as a passive warning, but the credentials still are honored, if some node red configuration setting is set to allow same? Maybe an override option in the settings.js file?