-
Notifications
You must be signed in to change notification settings - Fork 297
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
Deprecations and breaking changes in 3.0.0 #1404
Milestone
Comments
note sure why you want to "Rename of ripencc_abuse_contact bot to ripe" ? This list of items is too terse for me. It's not publicly clear what you mean... deferring until this is clear. |
The list is a reminder on the actions I need to do before the 3.0.0. Most of them are components which are already marked deprecated and announced to be removed in the version 3.0. |
ghost
pushed a commit
that referenced
this issue
Jun 17, 2021
was renamed and marked as deprecated in 2.0.0.beta1 #1404
ghost
pushed a commit
that referenced
this issue
Jun 17, 2021
Compatibility with the deprecated configuration format (before 1.0.0.dev7) was removed. #1404
Merged
ghost
pushed a commit
that referenced
this issue
Jun 17, 2021
compatibility with the deprecated parameter `unzip_attachment` (removed in 2.1.0) was removed. #1404
ghost
pushed a commit
that referenced
this issue
Jun 17, 2021
the init contained a fallback method if a parameter does not exist this is no longer necessary, as all bots have proper default values related to #1404
ghost
pushed a commit
that referenced
this issue
Jun 17, 2021
create_request_session_from_bot was deprecated and is no longer used #1404
ghost
pushed a commit
that referenced
this issue
Jun 17, 2021
The deprecated shell scripts - `update-asn-data` - `update-geoip-data` - `update-tor-nodes` - `update-rfiprisk-data` have been removed in favor of the built-in update-mechanisms (see the bots' documentation). A crontab file for calling all new update command can be found in `contrib/cron-jobs/intelmq-update-database`. #1404
ghost
pushed a commit
that referenced
this issue
Jun 21, 2021
was renamed and marked as deprecated in 2.0.0.beta1 #1404
ghost
pushed a commit
that referenced
this issue
Jun 21, 2021
Compatibility with the deprecated configuration format (before 1.0.0.dev7) was removed. #1404
ghost
pushed a commit
that referenced
this issue
Jun 21, 2021
compatibility with the deprecated parameter `unzip_attachment` (removed in 2.1.0) was removed. #1404
ghost
pushed a commit
that referenced
this issue
Jun 21, 2021
the init contained a fallback method if a parameter does not exist this is no longer necessary, as all bots have proper default values related to #1404
ghost
pushed a commit
that referenced
this issue
Jun 21, 2021
create_request_session_from_bot was deprecated and is no longer used #1404
ghost
pushed a commit
that referenced
this issue
Jun 21, 2021
The deprecated shell scripts - `update-asn-data` - `update-geoip-data` - `update-tor-nodes` - `update-rfiprisk-data` have been removed in favor of the built-in update-mechanisms (see the bots' documentation). A crontab file for calling all new update command can be found in `contrib/cron-jobs/intelmq-update-database`. #1404
waldbauer-certat
pushed a commit
that referenced
this issue
May 31, 2022
was renamed and marked as deprecated in 2.0.0.beta1 #1404
waldbauer-certat
pushed a commit
that referenced
this issue
May 31, 2022
Compatibility with the deprecated configuration format (before 1.0.0.dev7) was removed. #1404
waldbauer-certat
pushed a commit
that referenced
this issue
May 31, 2022
compatibility with the deprecated parameter `unzip_attachment` (removed in 2.1.0) was removed. #1404
waldbauer-certat
pushed a commit
that referenced
this issue
May 31, 2022
the init contained a fallback method if a parameter does not exist this is no longer necessary, as all bots have proper default values related to #1404
waldbauer-certat
pushed a commit
that referenced
this issue
May 31, 2022
create_request_session_from_bot was deprecated and is no longer used #1404
waldbauer-certat
pushed a commit
that referenced
this issue
May 31, 2022
The deprecated shell scripts - `update-asn-data` - `update-geoip-data` - `update-tor-nodes` - `update-rfiprisk-data` have been removed in favor of the built-in update-mechanisms (see the bots' documentation). A crontab file for calling all new update command can be found in `contrib/cron-jobs/intelmq-update-database`. #1404
waldbauer-certat
pushed a commit
that referenced
this issue
Jul 15, 2022
was renamed and marked as deprecated in 2.0.0.beta1 #1404
waldbauer-certat
pushed a commit
that referenced
this issue
Jul 15, 2022
Compatibility with the deprecated configuration format (before 1.0.0.dev7) was removed. #1404
waldbauer-certat
pushed a commit
that referenced
this issue
Jul 15, 2022
The deprecated shell scripts - `update-asn-data` - `update-geoip-data` - `update-tor-nodes` - `update-rfiprisk-data` have been removed in favor of the built-in update-mechanisms (see the bots' documentation). A crontab file for calling all new update command can be found in `contrib/cron-jobs/intelmq-update-database`. #1404
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ripencc_abuse_contact
bot toripe
intelmqdump
: Integratee
ind
and renamev
toe
.bots/experts/modify/expert.py
bots.collectors.rt.collector_rt
parameterunzip_attachment
intelmq.bots.experts.reverse_dns.expert
parameteroverwrite
-> False (Reverse DNS and Cymru Whois default overwrite #1452)intelmq.bots.experts.cymru_whois.expert
parameteroverwrite
-> False (Reverse DNS and Cymru Whois default overwrite #1452)intelmq.bots.experts.modify.expert
parameteroverwrite
-> Falsecontrib/cron-jobs/intelmq-update-data
: removeintelmq.lib.utils.create_request_session_from_bot
: removeupdate-asn-data
update-geoip-data
update-tor-nodes
update-rfiprisk-data
Postponed from 2.0.0 (#1125):
Backwards compatibility on extra field with type JSON (see Access extra.* like normal fields #1046) -- need to evaulate usagenot trivial -> postponedThe text was updated successfully, but these errors were encountered: