Skip to content

Conversation

cstns
Copy link
Contributor

@cstns cstns commented Oct 2, 2025

Description

Add a team selection step when deploying blueprints.

  • the team step should only be accessible when deploying blueprints and the user is a member in multiple teams

Related Issue(s)

closes #6098

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.
    -bugfix, not needed

Labels

  • Includes a DB migration? -> add the area:migration label

@cstns cstns requested a review from knolleary October 2, 2025 14:24
Copy link

codecov bot commented Oct 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.81%. Comparing base (a03f01a) to head (5f27d2f).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6099   +/-   ##
=======================================
  Coverage   76.81%   76.81%           
=======================================
  Files         380      380           
  Lines       19230    19230           
  Branches     4624     4624           
=======================================
  Hits        14771    14771           
  Misses       4459     4459           
Flag Coverage Δ
backend 76.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cstns cstns self-assigned this Oct 2, 2025
Copy link
Member

@knolleary knolleary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified with both a user with multiple teams (they are shown the choice of teams) and a user with a single team (they are not shown the choice).

@cstns cstns merged commit 4d412ea into main Oct 8, 2025
23 checks passed
@cstns cstns deleted the team-selection-when-deploying-a-blueprint branch October 8, 2025 09:11
@knolleary
Copy link
Member

@cstns my apologies - not sure why I didn't merge it after approval - think I was waiting for the tests to pass but failed to come back.

@cstns
Copy link
Contributor Author

cstns commented Oct 8, 2025

No worries!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deploying a blueprint is limited to the default team

2 participants