Add ability to deploy helm v3

[AblionGE]

fix tests

add unit test for helm_repo

removing helm 3 option in helm init

[puppet-community-rangefinder]

helm::config is a class

that may have no external impact to Forge modules.

helm::helm_init is a type

that may have no external impact to Forge modules.

helm::params is a class

that may have no external impact to Forge modules.

helm::repo is a type

that may have no external impact to Forge modules.

helm::repo_update is a type

that may have no external impact to Forge modules.

This module is declared in 0 of 575 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[codecov-io]

Codecov Report

Merging #129 (3f06984) into main (94fd36d) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #129   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files         10      10           
  Lines        259     259           
=====================================
  Misses       259     259           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 94fd36d...3f06984. Read the comment docs.

[AblionGE]

Hi,
I'm back with a new pull request for Helm 3 !
I was not able to run acceptance test due to a vagrant issue...

[edomaur]

Code seems to be clean, and testing deployment of helm3 seems to work as intended.

[daianamezdrea]

Hi @AblionGE ! Thank you for your PR, it looks very nice, IAC team has the Triage day on Monday when I will test your changes! Cheers!

[daianamezdrea]

Hi @AblionGE, I'm seeing this error on both centos7 and ubuntu 16.04 :
Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, 'split' parameter 'str' expects a String value, got Undef (file: /etc/puppetlabs/code/environments/production/modules/helm/manifests/repo.pp, line: 79, column: 18)
I'm currently looking to see what is happening, thank you for your patience !

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Marc Schaer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[daianamezdrea]

Hi @AblionGE , we have some dependency failures on ubuntu ( I'm currently working in solving the problem) and after this your PR will be tested on a clean base, thank you!

[daianamezdrea]

Hi @AblionGE, we added Github Action for our tests, could you re-base your PR? Thank you!

[AblionGE]

Hello @daianamezdrea , Rebase done but integration testings are not passing. Is my rebase correct ?

[github-actions]

This PR has been marked as stale because it has been open for a while and has had no recent activity. If this PR is still important to you please drop a comment below and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days.

[treydock]

I think this PR needs to be redone to fully remove Helm v2 support to simplify the module. Helm v2 has long been EOL.

[github-actions]

Hello! 👋

This pull request has been open for a while and has had no recent activity. We've labelled it with attention-needed so that we can get a clear view of which PRs need our attention.

If you are waiting on a response from us we will try and address your comments on a future Community Day.

Alternatively, if it is no longer relevant to you please close the PR with a comment.

Please note that if a pull request receives no update for 7 after it has been labelled, it will be closed. We are always happy to re-open pull request if they have been closed in error.