flowfuse/github-actions-workflows

General purpose reusable Github Action workflows

FlowFuse helps Node-RED developers deliver applications in a more reliable, collaborative and secure manner. Node-RED’s intuitive, low-code development environment is great for connecting together hardware devices, APIs and online services. FlowFuse adds to Node-RED collaborative development, management of remote deployments, support for DevOps deliver pipelines, and the ability to host Node-RED applications on FlowFuse Cloud. FlowFuse is the devops platform for Node-RED application development and delivery.

Key Features

• FlowFuse adds team collaboration to Node-RED, allowing multiple developers to work together on a single instance.
• Many organizations deploy Node-RED instances to remote servers or edge devices. FlowFuse automates this process by creating snapshots on Node-RED instances that can be deployed to multiple remote targets.
• FlowFuse simplifies the software development lifecycle of Node-RED applications. You can now set up DevOps delivery pipelines to support development, test and production environments for Node-RED application delivery.
• FlowFuse is available from FlowFuse Cloud, a managed cloud service, or a self-hosted solution.
• FlowFuse offers professional technical support for FlowFuse and Node-RED.

Links

• Home Page
• Documentation
• Contributing
• Code of Conduct
• Security
• License

github-actions-workflows's Issues

Extend helm deployment workflow by adding helm diff

Description

The idea is to run helm upgrade diff against all environments instead of running deployment to non-production environments from PR. The diff results for each environment could be added to the PR. Once an operator is happy about the result, merge to the main branch should trigger deployment.
Diff could be part of the existing helm deployment workflow. It could use additional input variable like deploy_branch which will indicate the only branch from which deployment could be made. From all other branches, only helm diff will be performed.

container security scan should publish its report in Github Security tab

Description

Instead of publishing scan results as a part of PR, results should be visible in the Security tab, in the Code Scanning section.

Epic/Story

No response

Enable main branch protection and require reviews on PRs

Description

As this repo provides critical infrastructure we need to apply our standard security policies. Primarily:

• main branch protection
• require at least 1 review on all PRs

Epic/Story

No response