Skip to content

Conversation

bobtfish
Copy link
Contributor

This makes things work for me if you have the strict_variables setting set to true.

@igalic
Copy link
Contributor

igalic commented Jul 21, 2014

But fails for everyone else now :(

@bobtfish
Copy link
Contributor Author

hehe, damn, sorry - I'll loop back on this today, and see if I can get travis to like both types (and maybe even test both settings!)

@igalic
Copy link
Contributor

igalic commented Jul 22, 2014

Excellent. Now we only fail on Ruby 1.8, which seems to be a Travis issue.

@bobtfish
Copy link
Contributor Author

Ping! Is there anything blocking this from being merged?

@bobtfish bobtfish force-pushed the fix_strict_variables branch from 4759120 to 032f93a Compare September 22, 2014 21:43
@bobtfish
Copy link
Contributor Author

I've just rebased this to master

@spuder
Copy link

spuder commented Sep 22, 2014

+1

To test this, I had to update my .fixtures.yaml

  repositories:
    stdlib: 
      repo: "git://github.com/bobtfish/puppetlabs-stdlib.git"
      ref: "origin/fix_strict_variables"
  symlinks:
    gitlab: "#{source_dir}"

Then run the following commands

export STRICT_VARIABLES=yes
rake spec_prep
rake spec

With this fix, spec tests no longer give errors if using a custom fact and strict variables are turned on
spuder/puppet-gitlab@e55560a

$local_operatingsystem_lowercase=getvar("::operatingsystem_lowercase")
$gitlab_url = "${download_prefix}/$local_operatingsystem_lowercase-${::operatingsystemrelease}/${omnibus_filename}"

@igalic
Copy link
Contributor

igalic commented Sep 24, 2014

@hunner ping

hunner added a commit that referenced this pull request Sep 24, 2014
@hunner hunner merged commit 0cd08b3 into puppetlabs:master Sep 24, 2014
@bobtfish
Copy link
Contributor Author

👍 thank you!

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 this pull request may close these issues.

6 participants