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

Improper handling of download_url parameter #65

Closed
cardil opened this issue Mar 3, 2016 · 1 comment · Fixed by #80
Closed

Improper handling of download_url parameter #65

cardil opened this issue Mar 3, 2016 · 1 comment · Fixed by #80
Assignees
Labels

Comments

@cardil
Copy link
Collaborator

cardil commented Mar 3, 2016

download_url parameter in main class jboss has been moved to params file in commit 26c7345 (PR #26). This causes numerous issues when overriding $product or $version parameters using main class. Like this:

class { 'jboss':
  product => 'wildfly',
  version => '9.0.2.Final',
}

In this example $download_url is being resolved in params.pp file and default values of $product and $version are being used.

There are 2 propositions to fix this:

Move download_url to runtime class and calculate there

  • Moving $download_url to jboss::internal::runtime class
  • Set parameters from jboss class to jboss::internal::runtime class
  • Use parameters from jboss::internal::runtime class instead of params.pp
  • Update all references to $jboss::internal::runtime::download_url instead of $jboss::params::download_url

Calculate in params using product and version in runtime class

  • Set parameters from jboss class to jboss::internal::runtime class
  • Use parameters from jboss::internal::runtime class instead of params.pp
@cardil cardil added the bug label Mar 3, 2016
@cardil cardil added this to the v1.0.4 - WildOpal milestone Mar 3, 2016
@Cosaquee
Copy link
Contributor

Cosaquee commented Mar 3, 2016

I think that first option is better so i will do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants