Make blueprints accessible outside of "Create Instance" menu #3752
Conversation
Fix bug where the shared flow page was not loaded after refresh
…om the team library
cstns
added
the
area:frontend
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3752 +/- ##
==========================================
- Coverage 41.76% 41.71% -0.06%
==========================================
Files 647 650 +3
Lines 24768 24801 +33
Branches 6076 6084 +8
==========================================
Hits 10345 10345
- Misses 14423 14456 +33
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
joepavitt
changed the title
…t-accessibility # Conflicts: # frontend/src/pages/team/Library/TeamLibrary.vue
…t-accessibility # Conflicts: # frontend/src/pages/instance/Editor/index.vue
|
Have hit a blocker on this, when trying to start an instance that was created via the new library > blueprint workflow, instances crash to to false dependencies. Here on our blueprint, we have defined no modules: 
Note it's trying to add the blueprint's piece as a instance dependency: 
|
|
Turns out the above was my problem, the blueprints config just needs to be an empty object |
Description
Adds the ability to visualize existing blueprints and use them when creating instances.
Related Issue(s)
closes #3729
Checklist
I have read the contribution guidelinesDocumentation has been updatedUpgrade instructionsConfiguration detailsConceptsChangesflowforge.yml?Issue/PR raised onFlowFuse/helmto update ConfigMap TemplateIssue/PR raised onFlowFuse/CloudProjectto update values for Staging/ProductionLabels
Backport needed? -> add thebackportlabelIncludes a DB migration? -> add thearea:migrationlabel