Migrate Bolt modules to use GH Actions workflow for release
Closed this issue · 3 comments
Use Case
The IAC team recently developed a Github Actions workflow for releasing modules to the Forge, which gives us better control over the environment modules are released in and means we don't have to make changes in CI Job Configs to update module release pipelines. We piloted a new GH Action release workflow that is manually triggered which tags and then release modules with the PKCS7 module which worked great. Now that it's proven out, we should remove our current module release pipelines from CI Job Configs and create GH Action workflows that copy the workflow from pkcs7.
The apply_helpers module 0.3.0 did not get pushed to forge, it is part of https://github.com/puppetlabs/ci-job-configs/blob/8ae5544231244a57c67fdea1df525e7b4187c609/jenkii/platform/projects/bolt.yaml#L280 can we do a push then when that gets ported over as part of this work?
Sure - the workflow will tag the repo, and I'm not entirely sure what it'll do if the tag already exists....but we can try.
To review
- puppetlabs/puppetlabs-apply_helpers#11
- puppetlabs/puppetlabs-powershell_task_helper#5
- puppetlabs/puppetlabs-python_task_helper#19
- puppetlabs/puppetlabs-ruby_task_helper#19
- puppetlabs/puppetlabs-ruby_plugin_helper#4
- puppetlabs/puppetlabs-azure_inventory#15
- puppetlabs/puppetlabs-aws_inventory#20
- puppetlabs/puppetlabs-gcloud_inventory#13
- puppetlabs/puppetlabs-http_request#12
- puppetlabs/puppetlabs-secure_env_vars#4
- puppetlabs/puppetlabs-terraform#25
- puppetlabs/puppetlabs-vault#17
- puppetlabs/puppetlabs-yaml#6
- https://github.com/puppetlabs/ci-job-configs/pull/7889