Thomas Heartman 80a2e1b93f fix: reject API admin tokens when importing features (#4016) ... This PR fixes an issue where trying to use an admin token to import features via the API resulted in a 500 (due to missing properties). The solution is to catch when the user is using and admin token in the controller, throw a 400, and tell them to use personal access tokens or service accounts. The PR includes a new test file for this specific use case. We don't really test these cases many other places, so it seemed the logical choice.		2023-06-20 12:57:59 +00:00
..
createExportImportService.ts	feat: context field usage backend (#3921)	2023-06-09 12:00:17 +03:00
export-import-api-usage.test.ts	fix: reject API admin tokens when importing features (#4016)	2023-06-20 12:57:59 +00:00
export-import-controller.ts	fix: reject API admin tokens when importing features (#4016)	2023-06-20 12:57:59 +00:00
export-import-permissions.e2e.test.ts	feat: add import export flag (#3411)	2023-03-29 09:19:33 +03:00
export-import-service.ts	fix: filter out usage for export (#4006)	2023-06-19 13:42:55 +03:00
export-import.e2e.test.ts	fix: don't create duplicate tags on import (#3688)	2023-05-04 22:19:00 +02:00
import-context-validation.test.ts
import-context-validation.ts
import-permissions-service.ts
import-toggles-store-type.ts
import-toggles-store.ts	feat: promote toggles script (#3639)	2023-04-28 09:08:12 +02:00
import-validation-messages.ts