Every Nullstone module uses a small GitHub Actions workflow to publish new versions of modules.
Additionally, this requires configuring a Nullstone API Key as a secret in each repo.
Instead, a module creator should be able to connect a module to a source repo.
Also, the user should be able to configure the module with auto-publish with the following:
Auto-publish disabled.
Auto-publish on new semantic version tags pushed.
Auto-publish on new commits to default (master/main) branch. (Use --version=next-patch)
Auto-publish on commits in a PR (Use --version=next-build)
A module creator should be able to configure the following for auto-publish:
A list of files (globbing allowed) to watch. If any files change, a publish is triggered. (If users use this, they will typically use a single directory - e.g. tf/)
A list of files (globbing allowed) included in the published package. By default, this should include *.tf, *.tf.tmpl, and README.md.
Every Nullstone module uses a small GitHub Actions workflow to publish new versions of modules. Additionally, this requires configuring a Nullstone API Key as a secret in each repo.
Instead, a module creator should be able to connect a module to a source repo. Also, the user should be able to configure the module with auto-publish with the following:
master/main) branch. (Use --version=next-patch)A module creator should be able to configure the following for auto-publish:
tf/)*.tf,*.tf.tmpl, andREADME.md.