Comments (5)
We set $tomcatPort = 8080, in the init.pp.
from puppet-jira.
Yes but init.pp doesn't call ::jira::facts so it can't access $tomcatPort.
If I don't explicitly set $port when declaring the facts class i.e.
class { '::jira::facts':
port => '8080',
}
then /etc/facter/facts.d/jira_facts.rb looks like:
require 'json'
require 'open-uri'
begin
url = 'http://127.0.0.1:/rest/api/2/serverInfo'
info = open(url, &:read)
rescue
exit 0
end
.....
from puppet-jira.
Strange, we are sourcing the value from the main class. $port = $jira::tomcatPort,
You can confirm you are calling the main class? So your manifest should be something like:
class {'jira': }
class { 'jira::facts': }
I added a test for this, and it is detecting the port value from the main class. Assuming you are doing the above, can you confirm your version of puppet and ruby?
from puppet-jira.
My apologies, I had jira::facts declared before the main class so $port wasn't available when jira::facts was declared. I don't know if this is worth pointing out in the docs.
Thanks for the awesome module and quick upgrade to 6.4 today!
from puppet-jira.
For the next release jira::facts will be a private class and included by default. I recently did this for the stash module and noone has complained :)
Thanks for taking the time to log issues btw, I do appreciate it.
If its not to much trouble, please rate the module on the forge (Thanks in advance).
from puppet-jira.
Related Issues (20)
- Add optional MySQL connection string options HOT 1
- Jira_facts deprecation warnings HOT 1
- jira::java_opts defined as YAML multiline block string generates incorrect JAVA_OPTS string in setenv.sh HOT 2
- server.xml - StuckThreadDetectionValve introduced in 7.6.12
- Drop Ubuntu 16.04, Add 18.04 instead
- 5.0.0 release summary
- Test with Puppet 7 and fresher OSes
- JIRA will not start if the installation directory mode is missing o+x HOT 2
- connection-settings parameter in dbconfig.xml template should be connection-properties instead
- Manage web.xml Config HOT 1
- Release a new Jira version
- Add manage_homedir support
- scheme written twice in server.xml when using tomcat_native_ssl and supplying proxy settings
- cluster node id is too long using fqdn
- AlmaLinux support
- Release v5.2.0 HOT 2
- cluster.properties.epp - soon to be deprecated code by Puppet 8 HOT 1
- JVM_OPENS not set for JIRA Java 17 support
- Optional[Integer[-1]] $pool_max_wait breaks with latest puppet agent (7.29 or 8.5) HOT 3
- Jira cluster and NGINX Plus as the load balancer
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppet-jira.