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

Make type required when creating an escalation policy step #4356

Merged
merged 3 commits into from
May 20, 2024

Conversation

matiasb
Copy link
Contributor

@matiasb matiasb commented May 16, 2024

@matiasb matiasb added pr:no public docs Added to a PR that does not require public documentation updates release:ignore PR will not be added to release notes labels May 16, 2024
@matiasb matiasb requested a review from a team as a code owner May 16, 2024 18:57
@matiasb matiasb force-pushed the matiasb/escalation-policy-required-step branch from d0d2898 to 3233748 Compare May 16, 2024 20:06
@@ -303,8 +303,11 @@ def test_should_be_considered_for_rbac_permissioning(
NUM_ORGS = 5
settings.CLOUD_RBAC_ROLLOUT_PERCENTAGE = rollout_percentage

# make sure there are no other orgs around
Organization.objects.all().delete()
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we do this in a different way? Scary if someone runs this test connected to the wrong environment.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

After checking with Joey, it seems we can delete this test (RBAC rollout is already in progress and this will be cleanup soon anyways).
FWIW, we shouldn't run tests affecting any real db in any case, right? (they would break lots of things independently of this particular bit :-))

@matiasb matiasb force-pushed the matiasb/escalation-policy-required-step branch from 3233748 to 6093a3f Compare May 20, 2024 12:59
@matiasb matiasb added this pull request to the merge queue May 20, 2024
Merged via the queue into dev with commit 3c58c2f May 20, 2024
21 checks passed
@matiasb matiasb deleted the matiasb/escalation-policy-required-step branch May 20, 2024 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:no public docs Added to a PR that does not require public documentation updates release:ignore PR will not be added to release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants