Cant sync policies

[Eggwise]

Cant sync policies collection with directus-sync

Invalid enum value in directus-sync onlyCollections configuration (policies)

Description

When running directus-sync push command, the tool fails with an enum validation error for the onlyCollections configuration. The tool doesn't accept 'policies' as a valid collection name, despite it being a standard Directus collection type.

Steps to Reproduce

1. Configure baseConfig.js with the following collections:

module.exports = {
  onlyCollections: [
    'roles',
    'permissions',
    'settings',
    'folders',
    'flows',
    'operations',
    'presets',
    'policies',
  ],
};

2. Run the directus-sync push command.

directus-sync push

2. Run directus-sync push command

Current Behavior

The command fails with the following error:

ERROR: Config file: [onlyCollections,7] Invalid enum value. Expected 'dashboards' | 'flows' | 'folders' | 'operations' | 'panels' | 'permissions' | 'presets' | 'roles' | 'settings' | 'translations', received 'policies'

Expected Behavior

The 'policies' collection should be accepted as a valid collection type for synchronization, as it is a standard Directus system collection.

Environment

"directus-extension-sync": "3.0.2"

• Node.js version: v20.12.2 (NVM)
• Operating System: Macbook pro M2

Additional Context

The error occurs in the Zod schema validation within the directus-sync tool. The enum of allowed collections appears to be missing the 'policies' collection type, despite it being a valid Directus system collection.

[Eggwise]

when i use pnpm exec instead of npx it works, seems like a weird cache thing ?

[EdouardDem]

@Eggwise It's wreid because the policies is in the Collection enum used by Zod :

directus-sync/packages/cli/src/lib/services/config/schema.ts

Line 10 in e647a2d

'policies',

Did you use an old version of directus-sync (not directus-extension-sync) ?