Shared Environment Variables

[MarianRaphael]

Description

As a Node-RED developer and FlowForge user,
I want to share environment variables at various scopes - global, team, and application,
So that I can efficiently manage and organize variables according to their usage and scope, increasing the maintainability of our projects.

Which customers would this be availble to

Licensed Edition (EE)

Acceptance Criteria

• appropriate access controls to ensure that only authorized users can create, modify, or delete variables at each scope level
• creation and management of environment variables at different levels of scope: global, team, and application

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[joepavitt]

Quick sketch for how we could display inherited variables:

Interactive prototype: https://www.figma.com/proto/rMB2w5ZZUtTC0nxbwLYKJY/FlowForge-Platform?page-id=0%3A1&type=design&node-id=1825-9798&viewport=-11497%2C-12013%2C0.83&scaling=min-zoom&starting-point-node-id=1825%3A9798&show-proto-sidebar=1&mode=design&t=TpsS6Yz5AUNWfcma-1

[ZJvandeWeg]

@joepavitt Can we reuse the right most column for the overwritten value icon, or when it's inherited from a group?

[joepavitt]

Had considered that, but it can be both inherited and locked or deprecated...

[joepavitt]

Also wanted to make more explicit differentiation between locally/newly defined vars, and inherited

[ZJvandeWeg]

Deprecated we can remove through a migration. We add them to each instance in the db, and remove their default status.

Inherited cannot be locked, so the left bar is available?

Also wanted to make more explicit differentiation between locally/newly defined vars

Can you elaborate?

[joepavitt]

Inherited cannot be locked, so the left bar is available

Why not? If I define a common env var at the Team/Application level that I want set, and not changed, across all instances, then that's both locked and inherited?

[joepavitt]

Deprecated we can remove through a migration

I suspect this isn't that simple as possibly customer flows that are using these deprecated env vars?

[ZJvandeWeg]

@joepavitt If we explicitly set them instead, than the new instances don't need them to be set anymore.

[joepavitt]

Removed icon int he value cell, but kept the one left-most

[joepavitt]

Can you elaborate?

I felt like (happy to validate of course) that when viewing the Environment Variables at an Instance-level, you'd want to know, clearly, which ones were defined above (at Application/Team) and which ones were bespoke for this Instance.