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

Describe how to suppress resource conflicts #25

Merged
merged 1 commit into from
Oct 2, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,16 @@ For `notify` operation you need to provide `base-url` to fetch previous conflict
Other application configuration that are not supplied via command line are provided in this [application.conf](https://github.com/RIPE-NCC/nro-delegated-stats/blob/main/src/main/resources/application.conf)
which by default is bundled, but can be overriden using `-Dconfig.file=<application.conf>`.


## Adding conflict exceptions

There are conflicts in certain resource attribution and these conflicts are mentioned in the `conflicts` generated
in the result directory for every date. Some of these conflicts are historically justified in some way or the other
and are pretty hard to get rid of administratively. If RS gives up on some of the conflicts, we have `allowedlist`
file to add them to. After adding resources to `allowedlist` they are not mentioned in the notification email sent
to RS on the daily basis. The easiest way of suppressing conflict notifications is to copy-paste the line (any of
the two conflicting lines) from `conflicts` to the `allowedlist` and rebuild the docker image by creating a new release.

## License

Copyright (c) 2019-2022 RIPE NCC All rights reserved.
Expand Down
Loading