It may be useful for a collection to be able to define custom build related options.
Like:
file inclusion/exclusion/ignore patterns that may differ from collection to collection.
if scm specific file excludes should be honored, once mazer learns how to use them (For cases where the scm ignore files don't make sense for 'mazer build' like autogenerated modules)
if SPDX compat licenses should be enforced.
It may also be useful to support configuring these in the mazer.yml config file, for use when building any collection.
Example use: a user who uses Revisions-R-Us source control tools may want to ignore .revisions-r-us* for all builds. Since no one else uses Revisions-R-Us it wouldn't seem worth adding to the mazer builtin ignore lists.
Related to: https://github.com/ansible/mazer/issues/195 - use scm ignore files for mazer build https://github.com/ansible/mazer/issues/168 - support building artifacts that do not use SPDX licenses
It may be useful for a collection to be able to define custom build related options. Like:
It may also be useful to support configuring these in the mazer.yml config file, for use when building any collection.
Example use: a user who uses Revisions-R-Us source control tools may want to ignore .revisions-r-us* for all builds. Since no one else uses Revisions-R-Us it wouldn't seem worth adding to the mazer builtin ignore lists.