Skip to content

Conversation

@Christinarlong
Copy link
Contributor

When I was testing the frontend for the multi org flow, I realized I could

  1. Start the installation flow on Org1, which did not have business plan
  2. Start the installation flow on Org2, which did have business plan
  3. Switch back to the OrganizationSelection UI/screen on Org1 -> refresh -> Now able to select a GH organization to multi org with

It looks like in the pipeline, Org2 was being used as the active organization, but the installation still installed on Org1 🤷‍♀️

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 2, 2025
@Christinarlong Christinarlong marked this pull request as ready for review June 2, 2025 22:43
@Christinarlong Christinarlong requested review from a team as code owners June 2, 2025 22:43
Copy link
Member

@leeandher leeandher left a comment

Choose a reason for hiding this comment

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

LGTM! one comment about potentially exiting the pipeline entirely with a new error, though you're more familiar with this flow so I'll defer to your judgment 🚀

and installing_organization_slug
== self.active_user_organization.organization.slug
)
if not has_scm_multi_org or not is_same_installing_org:
Copy link
Member

Choose a reason for hiding this comment

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

Good catch! But should we handle this with a separate error more generally, like break the pipeline if the user is seeing resources from a different organization after re-fetching? I'll leave it to you but I think that switching organizations mid installation is totally fine to break the installation flow.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ooo that makes sense uh, I just would need to figure out how to do that in the frontend :hides:

@Christinarlong Christinarlong merged commit 0a5787f into master Jun 5, 2025
61 checks passed
@Christinarlong Christinarlong deleted the crl/check-same-org-after-org-selection branch June 5, 2025 17:18
@github-actions github-actions bot locked and limited conversation to collaborators Jun 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants