You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: JSON.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,9 +174,10 @@ The modules inside `build`, `provides`, and `index` use these fields:
174
174
For `provides` and `index` dictionaries, this name must be the key of each entry (not a field inside).
175
175
For the `build` array, it must be inside each module object (with `name` as the key).
176
176
Local modules (files and folders in same directory as `cfbs.json`), must start with `./`, and end with `/` if it's a directory.
177
+
Absolute modules (a directory given by absolute path containing a Git repository) must start with `/` and end with `/`.
177
178
Module names should not be longer than 64 characters.
178
-
Module names (not including adfixes `./`, `/`, `.cf`, `.json` for local modules) should only contain lowercase ASCII alphanumeric characters possibly separated by dashes, and should start with a letter.
179
-
Local module names can contain underscores instead of dashes.
179
+
Module names (not including adfixes `./`, `/`, `.cf`, `.json` for local and absolute modules) should only contain lowercase ASCII alphanumeric characters possibly separated by dashes, and should start with a letter.
180
+
Local and absolute module names can contain underscores instead of dashes.
180
181
-`description` (string): Human readable description of what this module does.
181
182
-`tags` (array of strings): Mostly used for information / finding modules on [build.cfengine.com](https://build.cfengine.com).
182
183
Some common examples include `supported`, `experimental`, `security`, `library`, `promise-type`.
0 commit comments