Why are "protected" resources (views and styles in Perspective) excluded from export features in Ignition designer? Is that a bug or a feature?
I expect I should be able to export "protected" resources for backup or for subsequent import on other systems. Am I wrong?
My impression from documentation is that the intent of the Protecting Project Resources features were more about limiting access to edit/modify them in-place. Seems odd to me that the "protected" resources are omitted from export capabilities.
I suspect the original intention (this seems to trace back as far as 7.7) was maybe that only a user with permission to edit or un-protect that resource could export it, and that intention may have been lost in translation as time went on... likely with the new project system introduced in 8.0.
FYI, in my example even the person who set the resource as protected (me) is unable to export it unless I unprotect it first, painful if I use resource protection widely, and prone to introduce WTF moments if I forget this tidbit of information.
What are the chances of this behavior getting changed in the near future (I'd guess chances are slim). Seems we need general clarification on whether the resource protection is about protecting against access/visibility, modification or both.
Personally I'd prefer it was only a check (road-bump) against modifying something in-place that your not supposed to edit and that it should not prevent export, copy, or viewing (read-only) even while protection is turned on. If ignition developers are on-board with my thoughts on the matter perhaps it would be more aptly be referenced as a read-only (or locked) flag on the resource.
Resource protection could be something more akin to to blocking any access to configuration for security or IP protection with per-resource role-based security applied... which I don't personally support or think necessary.
BTW, I'd also support the idea of allowing the user to open any resource in read-only mode so one can inspect without introducing changes
(and without creating conflicts with someone else viewing/editing the resource).
Don't know, I opened an issue internally, it will get reviewed by the appropriate product owner and team. If and when something happens from there is up to them.
