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
Circumvent approval of a facility by deleting and re-adding #922
Comments
Feels like a clear bug - do we need to discuss? +1 if so |
+1 |
Maybe related to or the same as "Creating a facility that matches the name of a soft-deleted facility will cause the entry to bypass the verification queue" #901 |
seems like a bug to me |
Seems like a bug or just PeeringDB accepting your choices "ok" :D
…On Fri, Jan 22, 2021 at 4:57 PM Arnold Nipper ***@***.***> wrote:
A user may circumvent the approval of a facility by deleting when in
status "pending" and then re-adding. The status then changes from "deleted"
to "ok" instead of "pending".
[image: 20210122-Version-History-PeeringDB]
<https://user-images.githubusercontent.com/16888757/105506512-6dc97300-5cca-11eb-851f-ed306af1a415.png>
@peeringdb/pc <https://github.com/orgs/peeringdb/teams/pc> please make up
your mind. @peeringdb/ac <https://github.com/orgs/peeringdb/teams/ac> you
may also want to comment
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#922>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOZM2AOCP22C36VXKA3JHH3S3GG7HANCNFSM4WOTGE5Q>
.
--
Yours Sincerely,
Yolandi Robinson
Email: yolandi@peeringdb.com
Skype: yolandi.robinson97
|
Clear bug (and +1 anyway). |
Summary
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A user may circumvent the approval of a facility by deleting when in status "pending" and then re-adding. The status then changes from "deleted" to "ok" instead of "pending".
@peeringdb/pc please make up your mind. @peeringdb/ac you may also want to comment
The text was updated successfully, but these errors were encountered: