The .vect folder contains all internal Vect configuration files. All of the files in .vect will be created automatically during onboarding, and can be edited through Vect editing tools. In the .vect you will find configurations for your client api-keys, schema validations, files synced with external resources (GitHub, GitLab, etc..), and the Endorsements flow.

Keep in mind that we assume a certain structure to the configuration, so make sure changes are aligned with current file structure:

• API Keys will be placed under .vect/authorizations/api-keys.json
• Recipes are placed under .vect/recipes
• Validations:

  • Schemas are placed under .vect/resources/<schema-type>/<schema-name>

  • Schemas to file mapping is defined in .vect/transformations

  • The json file assumes the following keys:

    • type - Type of the schema, can be either json-schema-validation or jtd-schema-validation
    • schemaFileName - Name of the specific schema
    • sourceFileGlobPattern - The glob pattern that matches the file, Read more about globs

    {
      "type": "json-schema-validation",
      "schemaFileName": ".vect/resources/json-schema-validation/features-schema.json",
      "sourceFileGlobPattern": "**/features/*"
    }