-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assign device group to pipeline stage #3229
Assign device group to pipeline stage #3229
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## 2997-device-group-frontend #3229 +/- ##
==============================================================
+ Coverage 40.52% 40.71% +0.18%
==============================================================
Files 597 598 +1
Lines 22063 22342 +279
Branches 5301 5387 +86
==============================================================
+ Hits 8941 9096 +155
- Misses 13122 13246 +124
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
New button also contains "Device" so need to be more specific
…up-to-pipeline-stage
…up-to-pipeline-stage
I've done a first pass here to get an overall idea, but need to go through again tomorrow with fresh eyes |
…abled Add device group feature flag in TeamType
…for-pipeline-stage-deploy Add missing audit logger for pipeline stage deploy
I've been through this again and nothing stood out, I'm still not feeling 100% about it yet, perhaps just because of the number of changes, but let's not block this any longer. |
Description
General
Add support for setting a Device Group as the target of a pipeline execution
Adds through table
PipelineStageDeviceGroups
Add unit tests
add e2e tests
Related Issue(s)
#2989
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
backport
labelarea:migration
label