Allianceauth-afat

Added

- Button to close your own ESI fleet to more view. It is now available on the
Dashboard, in the FAT link list and in the FAT link details view as well. You can
only close your own ESI fleets.

Changed

- Manual FAT function limited. It is only available when the FAT link has been
created within the last 24 hours and has not been re-opened.
- Message templates refactored to make them more maintainable

Changed

- Ability to manually add pilots to FAT link has been disabled for ESI tracked FAT
links. The reason for this is pretty simple. Since an ESI tracked FAT link is
continuously tracking the fleet via ESI, all pilot who have been in said fleet are
added automatically. If someone hasn't been added, said someone wasn't in the fleet.

⚠️ Important ⚠️

If you haven't updated to the v2 version yet, do so first and do not go straight to
this version. Read the [update instructions for v2.0.0 please](-update-instructions-for-v200-)
please.

Fixed

- `django.db.utils.IntegrityError: (1048, "Column 'log_time' cannot be null")` on
log merge.

⚠️ Important ⚠️

If you haven't updated to the v2 version yet, do so first and do not go straight to
this version. Read the [update instructions for v2.0.0 please](-update-instructions-for-v200-)
please.

______________________________________________________________________

If you are updating from one of the 2.0.0-alpha versions

If you installed one of the alpha versions, make sure to reset your migrations first!
Migrations have been reset during the alpha versions a couple of times.

To do so, run:

shell
python manage.py migrate afat 0017


Once done, proceed with the update as lined out below.

______________________________________________________________________

This release introduces a new periodic task, make sure to add it to your `local.py`,
besides that, it is the usual steps to update ...

Download and install the new version

shell
pip install -U allianceauth-afat


Add the new task to your `local.py`

python
CELERYBEAT_SCHEDULE["afat_logrotate"] = {
"task": "afat.tasks.logrotate",
"schedule": crontab(minute="0", hour="1"),
}


Run static collection and migrations

shell
python manage.py collectstatic
python manage.py migrate


Restart your supervisor.

Finally migrate the Manual FAT log to the new logging table

shell
python manage.py afat_migrate_manual_fat_log

⚠️ IMPORTANT ⚠️

Before you update to this version, make sure you remove all "deleted" data from
your tables. To do so, log in to your mysql console and run the following commands:

mysql
de-activate foreign key checks
SET FOREIGN_KEY_CHECKS=0;

remove all "deleted" FATs
delete from afat_afat where deleted_at is not null;

remove all "deleted" fat link types
delete from afat_afatlinktype where deleted_at is not null;

get all fatlink IDs of "deleted" fatlinks as comma separated list and make sure
to have that in your notepad saved, you need this list for the next comamnds
select group_concat(id) from afat_afatlink where deleted_at is not null;

now remove everything that is related to those IDs
make sure to replace "id_list" with the comma separated
list of IDs from the earlier command
delete from afat_clickafatduration where fleet_id in (id_list);
delete from afat_afat where afatlink_id in (id_list);
delete from afat_afatlink where id in(id_list);

re-activate foreign key checks
SET FOREIGN_KEY_CHECKS=1;


This step is important before updating, because the "deleted" marker will be lost
during migration! If you don't run this step, you'll have all your FATlinks and FATs
that were previously "deleted" as active again.

Removed

- Soft deletion mechanism we inherited from ImicusFAT. It's more trouble than it's worth
and it's not used anyways. So we stick to "delete data when it should be deleted",
and not just mark it as deleted and keep it as stale data in the table.

Updated

- Migration information for migration from ImicusFAT in README.md file

Added

- Ship type overview to FAT link detail page (72)