Separating Test & Production Environments

Did you know that in Crosser, you can have a separate development environment? This is crucial for maintaining a stable, efficient, and secure production environment while enabling a dynamic and flexible space for development activities

Creating distinct development/test environments is a fundamental practice, allowing thorough testing of new features, releases, and bug fixes before implementing them on the production platform.

The following features can be used to set up development environments in the Crosser platform:

• Role-based permissions using labels: 

• Create custom roles in the ‘Organization’ settings, where Node permissions are restricted using labels, e.g. ‘Dev’ and ‘Prod’. Assign these labels to the corresponding Nodes and give users roles that match their required access.

• You can then, for example, create custom roles for users that can only create, modify and test flows but prevent them from deploying.

• If you authenticate users through OpenID Connect you can map custom roles with your Identity Provider. 

• Flow sharing: 

• Access to Flows can be limited to specific users, using the ‘Share’ options in the Flow settings. While the Flow is under development, access can for example be limited to the user developing the Flow. When it’s ready for deployment it is shared with the user responsible for deployment on a specific Node.

• Categories can also come in handy, for example to keep new Flows in a ‘Under development’ category and then move them to a ‘Production’ category when they are ready for deployment. Then it’s less likely that an unfinished Flow is deployed in the production environment by mistake.

• Node types

• When registering new Nodes you need to specify if the Node is for ‘Production’ or ‘Dev and Test’.

• On the Monitoring pages, issues reported from ‘Dev and Test’ Nodes are not getting the same priority as issues from ‘Production’ Nodes.