Skip to content

Conversation

kamil-certat
Copy link
Contributor

The change has been proposed and discussed over
a year ago.

Compatibility: as no bot uses the field by default at the moment, there is no incompatibility risk if the local operator uses modified IDF schema or stores all data in e.g. SQL database. To prevent issues, until the next major release the official bots using the field should fall back to extra.<field name> if the field does not exist in the local IDF.

IEP: https://github.com/certtools/ieps/tree/main/008
Relevant discussion: https://lists.cert.at/mailman3/hyperkitty/list/[email protected]/thread/V2QC7GJGJEFE7VLAJDMDAABOCUZUUVKM/#MUIZIQIUTFL4VQQE4SHWKHIVZU2PJJT2

Copy link
Member

@sebix sebix left a comment

Choose a reason for hiding this comment

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

  • missing documentation in docs/user/event.md
  • missing documentation in NEWS.md

@sebix sebix added this to the 3.4.0 milestone Mar 3, 2025
@sebix
Copy link
Member

sebix commented Mar 7, 2025

Upgrade function in intelmq/lib/upgrades to update the harmonization.conf is missing too

@sebix sebix added the feature Indicates new feature requests or new features label Aug 18, 2025
@sebix sebix modified the milestones: 3.6.0, 3.5.0 Feature Release Aug 20, 2025
@sebix
Copy link
Member

sebix commented Aug 29, 2025

requires #2575 to be merged first, then we rebase this on on develop.

@sebix sebix changed the title Implementing IEP008 - contituency field Implementing IEP008 - constituency field Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-format feature Indicates new feature requests or new features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants