woodpecker-helm3/internal/run
Erin Call 588c7cb9f7
Initialize Steps with a NewSTEPNAME function [#67]
This seems to be be a more natural separation of concerns--the knowledge
of which config fields map to which parts of a Step belong to the Step,
not to the Plan.
2020-01-16 13:50:04 -08:00
..
addrepo.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
addrepo_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
cmd.go Brush all the lint off this code I wrote in a haze 2019-12-09 10:53:32 -08:00
cmd_test.go Very rough code that can helm install 2019-12-04 12:41:37 -08:00
config.go Put step-specific config in those steps [#61] 2020-01-02 11:38:41 -08:00
depupdate.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
depupdate_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
help.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
help_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
initkube.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
initkube_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
lint.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
lint_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
uninstall.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
uninstall_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
upgrade.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00
upgrade_test.go Initialize Steps with a NewSTEPNAME function [#67] 2020-01-16 13:50:04 -08:00