But.. we can have AspaDefinition and AspaProvidersUpdate and ASPA objects in history that use the limit.
Because we don't want to keep the old AFI limit concept and logic in our code, we will remove these events from history. Migration code for 0.14.0 will understand the old events to the point that it can work out the last state before the upgrade, so that it can then do a one-time re-import of that configuration (minus the afi limit) and generate v1 ASPA objects.
Pending sidrops aspa profile update..
The afiLimit will be removed.
But.. we can have
AspaDefinitionandAspaProvidersUpdateand ASPA objects in history that use the limit.Because we don't want to keep the old AFI limit concept and logic in our code, we will remove these events from history. Migration code for 0.14.0 will understand the old events to the point that it can work out the last state before the upgrade, so that it can then do a one-time re-import of that configuration (minus the afi limit) and generate v1 ASPA objects.