amarillo/amarillo-core
5
0
Fork 0
Code Issues 17 Pull requests Packages Projects Releases Wiki Activity

Change agencyconf to user dir and add permissions for users #19

New issue
Open
opened 2024-10-25 15:16:50 +02:00 by Frank · 4 comments
Frank commented 2024-10-25 15:16:50 +02:00
Owner
Copy link

As done in the OAuth fork. But without the OAuth.

As done in the OAuth fork. But without the OAuth.
Csaba was assigned by Frank 2024-10-25 15:16:50 +02:00
Frank added this to the Amarillo project 2024-10-25 15:16:50 +02:00
Csaba commented 2024-11-18 10:57:28 +01:00
Owner
Copy link

How should we ease the migration to this for existing instances? If there are a lot of agency configurations it is not viable to rename them manually

How should we ease the migration to this for existing instances? If there are a lot of agency configurations it is not viable to rename them manually
Csaba commented 2024-11-18 12:42:54 +01:00
Owner
Copy link

This is also a breaking API change as the gtfs exporter verifies the permission for triggering GTFS generation, so if i rename the router it is incompatible. This is something we will always have to watch out for

This is also a breaking API change as the gtfs exporter verifies the permission for triggering GTFS generation, so if i rename the router it is incompatible. This is something we will always have to watch out for
Frank commented 2024-11-21 13:11:06 +01:00
Author
Owner
Copy link

This is also a breaking API change as the gtfs exporter verifies the permission for triggering GTFS generation, so if i rename the router it is incompatible. This is something we will always have to watch out for

Iow, when core uses users instead of agencyconfs then all other plugins must be updated accordingly.
Older versions of core must use older versions of the plugins prior to the change.

> This is also a breaking API change as the gtfs exporter verifies the permission for triggering GTFS generation, so if i rename the router it is incompatible. This is something we will always have to watch out for Iow, when core uses users instead of agencyconfs then all other plugins must be updated accordingly. Older versions of core must use older versions of the plugins prior to the change.
Frank commented 2024-12-06 12:19:30 +01:00
Author
Owner
Copy link

We shall not do it automatically but on startup write a warning if it is wrong and tell the admin how to fix it, where to put the right files.

We shall not do it automatically but on startup write a warning if it is wrong and tell the admin how to fix it, where to put the right files.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
fastapi-enhancer
permissions
carpool-events
bearer-token
log-errors
grfs-export
docker-build-test
static-files
jenkins-test
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Amarillo
Assignees
Clear assignees
No assignees
Csaba
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: amarillo/amarillo-core#19
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?