Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Helm v3 (continued) #137

Closed
wants to merge 6 commits into from
Closed

Conversation

treydock
Copy link

@AblionGE and @daianamezdrea , this is a continuation of #129 but with some fixes. The main fix is you can't reference class parameters in defined type parameter defaults without ensuring that those classes are defined before the defined type, which isn't always the best as it makes Puppet code dependent on the order things are defined. Instead you have to include the class and then reference the parameters.

Also had to rename the spec file for acceptance as usually rspec expects spec files to end with _spec.rb

Feel free to make my changes in #129 if that's preferable.

@treydock treydock requested a review from a team as a code owner December 15, 2020 13:22
@puppet-community-rangefinder
Copy link

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 is a class

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 576 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
Copy link

codecov-io commented Dec 15, 2020

Codecov Report

Merging #137 (a1822a0) into main (94fd36d) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##            main    #137   +/-   ##
=====================================
  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...a1822a0. Read the comment docs.

@AblionGE
Copy link

Thanks @treydock for improving this !

@treydock
Copy link
Author

treydock commented Jan 14, 2021

Updated pull request to simplify logic on avoiding init and other things when doing Helm v3 because those things are not needed. For this most recent change the Puppet module was adding Kubernetes tiller resources like a ServiceAccount and that's not necessary with Helm v3 so this most recent change avoids unnecessary changes when install Helm v3, which should also reduce the diff size for entire pull request.

@treydock treydock force-pushed the pr-129 branch 2 times, most recently from 8a87cba to f15b92e Compare January 14, 2021 17:59
@sanfrancrisko sanfrancrisko self-assigned this Jan 25, 2021
@CLAassistant
Copy link

CLAassistant commented Feb 24, 2021

CLA assistant check
All committers have signed the CLA.

@daianamezdrea
Copy link
Contributor

Hi @treydock, 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
Copy link
Contributor

Hi @treydock, we added Github Actions for running our tests, can you rebase this PR? Thank you!

@treydock
Copy link
Author

I have rebased

@treydock
Copy link
Author

@daianamezdrea Is there a way to run integration tests outside Github Actions? Only 1 of the many tests failed and there is no useful output from the failure to tell me what went wrong so I'd like to test things locally but so far attempts to run the bolt commands locally has failed.

@daianamezdrea
Copy link
Contributor

daianamezdrea commented Jun 14, 2021

Hi @treydock, I was thinking at a way to get this tested and becaue the old way is not working anymore I have a suggestion that could help you:

  1. Clone kream repo, which will help you to spin up a cluster on your Mac/Linux ---> https://github.com/puppetlabs/kream
  2. Follow the commands:
    gem install bundler
    bundle install
    install kubectl (this needs to be applied according with your system)
    rake cluster_up
  3. install helm as here: https://github.com/puppetlabs/kream#helm
    If you want to use your branch for helm version , go to Puppetfile and add your branch there, like this:
    mod 'puppetlabs/helm', :git=> 'https://github.com/puppetlabs/puppetlabs-helm.git', :branch=> 'helm_test'

@daianamezdrea
Copy link
Contributor

Please try this and let me know if it works, sorry for my late answer, I was trying to find a good solution for the problem and then I forgot about it, thank you!

@chelnak chelnak closed this Mar 2, 2022
@chelnak chelnak reopened this Mar 2, 2022
@puppet-community-rangefinder
Copy link

helm_chart_update_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_create_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_delete_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_install_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_ls_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_package_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_repo_add_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_repo_remove_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm_repo_update_flags is a function

Breaking changes to this file MAY impact these 1 modules (near match):

helm::chart is a type

that may have no external impact to Forge modules.

helm::chart_update is a type

that may have no external impact to Forge modules.

helm::create is a type

that may have no external impact to Forge modules.

helm is a class

that may have no external impact to Forge modules.

helm::package 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 578 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.

@github-actions
Copy link

github-actions bot commented May 2, 2022

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.

@github-actions github-actions bot added the stale label May 2, 2022
@github-actions github-actions bot closed this May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants