Skip to content
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

Turn on LimitCollectionCreationDeletionSplit for self host #4808

Closed
wants to merge 1 commit into from

Conversation

addisonbeck
Copy link
Contributor

@addisonbeck addisonbeck commented Sep 26, 2024

🎟️ Tracking

🧵 Jira Ticket: PM-10863

📚 Stacked PRs

  1. server: Split LimitCollectionCreationDeletion into two database columns #4709
  2. server: Split Organization.LimitCollectionCreationDeletion into two separate business rules #4730
  3. clients: Split Organization.LimitCollectionCreationDeletion into two separate business rules clients#11223
  4. server: Turn on LimitCollectionCreationDeletionSplit for self host #4808
    ⬆️ YOU ARE HERE
  5. server: [PM-14821] [PM-14822] Remove LimitCollectionCreationDeletionSplit feature flag #4809
  6. clients: [PM-14821] Remove LimitCollectionCreationDeletionSplit feature flag clients#11258
  7. server: Drop LimitCollectionCreationDeletion from the database #4810

📔 Objective

🤳 The Bigger Picture

There is an option in the Admin Console that removes collection creation and
deletion controls from all organization members that are not in the Owner and
Admin roles. This PR stack splits this conjoined option into two separate
controls: one to block create operations and one to block delete
operations. This is a part of an effort to make these settings better align
with what customers expect it to do.

👉 This Pull Request 👍

Over the last two PRs we implemented the functional changes requested in this
body of work in server and clients. This PR is much more simple. It just
enables the feature for self hosted installations by manually setting the
feature flag to true.

This PR and the previous two in the stack encompass all of the functional
changes to the system in this PR stack. By now all requested functionality
should be deployed and available to customers. The next three pull requests
are maintenance tasks to support evolutionary database design and feature
toggling.

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

Copy link
Contributor

github-actions bot commented Sep 26, 2024

Logo
Checkmarx One – Scan Summary & Detailseb6fa4c1-ea63-4e3d-87c5-fd389d073372

Fixed Issues

Severity Issue Source File / Package
MEDIUM Unpinned Actions Full Length Commit SHA /build.yml: 579
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 153
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 96
MEDIUM Unpinned Actions Full Length Commit SHA /build.yml: 545
MEDIUM Unpinned Actions Full Length Commit SHA /build.yml: 664
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 168
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 160
MEDIUM Unpinned Actions Full Length Commit SHA /build.yml: 220
MEDIUM Unpinned Actions Full Length Commit SHA /build.yml: 616

@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/entity-updates branch from d2550af to 8d358e1 Compare September 26, 2024 18:33
@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/turn-on-for-self-host branch from 01daa33 to e2bf38b Compare September 26, 2024 18:34
Copy link

codecov bot commented Sep 26, 2024

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 42.66%. Comparing base (e16cad5) to head (a3599d8).
Report is 7 commits behind head on main.

Files with missing lines Patch % Lines
src/Core/Constants.cs 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4808      +/-   ##
==========================================
- Coverage   42.66%   42.66%   -0.01%     
==========================================
  Files        1411     1411              
  Lines       65087    65088       +1     
  Branches     5959     5959              
==========================================
  Hits        27772    27772              
- Misses      36075    36076       +1     
  Partials     1240     1240              

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


🚨 Try these New Features:

Copy link
Member

@eliykat eliykat left a comment

Choose a reason for hiding this comment

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

LGTM although we need to figure out the timing, see #4730 (comment).

@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/entity-updates branch 4 times, most recently from 0103218 to d9703a0 Compare October 4, 2024 18:17
@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/turn-on-for-self-host branch 2 times, most recently from 1a5cdd5 to 6510a44 Compare October 4, 2024 19:56
@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/entity-updates branch 2 times, most recently from 8561bc9 to 10c4aa7 Compare October 10, 2024 23:03
@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/turn-on-for-self-host branch from 6510a44 to 103f290 Compare October 10, 2024 23:19
@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/entity-updates branch 2 times, most recently from a7677cc to f769410 Compare October 15, 2024 23:42
Base automatically changed from ac/addison/pm-10863/entity-updates to main October 18, 2024 15:00
@addisonbeck addisonbeck force-pushed the ac/addison/pm-10863/turn-on-for-self-host branch from 103f290 to a3599d8 Compare November 18, 2024 18:24
@addisonbeck addisonbeck marked this pull request as ready for review November 18, 2024 18:24
@eliykat
Copy link
Member

eliykat commented Nov 19, 2024

Ignoring this as discussed given that you are planning on just removing the flagged code.

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.

2 participants