Jira (PUP-6446) Cant use 'master' or 'agent' as environment names
Title: Message Title Moses Mendoza commented on PUP-6446 Re: Cant use 'master' or 'agent' as environment names This ticket has not been updated in some time and is now being closed due to inactivity. This isn’t necessarily a statement that this ticket isn’t important - other issues may have demanded precedence since it was filed, or it may have simply slipped through the cracks. If any viewer/watcher feels closing this ticket is an error, please re-open it and add a comment explaining. Our apologies in advance for any mistake on this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6446) Cant use 'master' or 'agent' as environment names
Title: Message Title Henrik Lindberg assigned an issue to javipolo Puppet / PUP-6446 Cant use 'master' or 'agent' as environment names Change By: Henrik Lindberg Assignee: javipolo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6446) Cant use 'master' or 'agent' as environment names
Title: Message Title Henrik Lindberg commented on PUP-6446 Re: Cant use 'master' or 'agent' as environment names Is this still the case on 4.x? In 3.x the names you used (main, agent, master) are reserved as it is possible in 3.x. to create dynamic environments in the conf itself by simply using names other than those that have defined sections in the conf. Those so called "dynamic environments" are no longer supported. On puppet 4.x the environment name environment is reserved. (Have to check the documentation if other names are also reserved). If this ticket is for 3.x only, then we are not going to make changes (we cannot because of the dynamic environments). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6446) Cant use 'master' or 'agent' as environment names
Title: Message Title
javipolo updated an issue
Puppet / PUP-6446
Cant use 'master' or 'agent' as environment names
Change By:
javipolo
When using an environment named *master*, *agent* or *main*, it does not workHere I show having 2 environments named *production* and *master*When I get modulepath for *production* expansion is correctly done and everything works fine, but when I try to get it for *master* environment, it just prints the default basemodulepath{code} # Show environments config root@puppetmaster:~# grep environments /etc/puppet/puppet.confenvironmentpath = $confdir/environmentsroot@puppetmaster:~# # GOOD root@puppetmaster:~# cat /etc/puppet/environments/production/environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment production/etc/puppet/environments/production/modules:/etc/puppet/environments/production/external_modules:/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~# # WRONG root@puppetmaster:~# cat /etc/puppet/environments/master/environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment master/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~#{code}It's quite trivial to reproduce it, just create a new environment named after those reserved words ...
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop
Jira (PUP-6446) Cant use 'master' or 'agent' as environment names
Title: Message Title
javipolo updated an issue
Puppet / PUP-6446
Cant use 'master' or 'agent' as environment names
Change By:
javipolo
When using an environment named *master*, *agent* or *main*, it does not workHere I show having 2 environments named *production* and *master*When I get modulepath for *production* expansion is correctly done and everything works fine, but when I try to get it for *master* environment, it just prints the default basemodulepath{code}root@puppetmaster:~# grep environments /etc/puppet/puppet.confenvironmentpath = $confdir/environmentsroot@puppetmaster:~# cat /etc/puppet/environments/production/environment.conf modulepath=./modules:./external_modules:$basemodulepath root@puppetmaster:~# cat /etc/puppet/environments/ master production /environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment production/etc/puppet/environments/production/modules:/etc/puppet/environments/production/external_modules:/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~# root@puppetmaster:~# cat /etc/ puppet /environments/master/environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment master/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~#{code}It's quite trivial to reproduce it, just create a new environment named after those reserved words ...
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscr
Jira (PUP-6446) Cant use 'master' or 'agent' as environment names
Title: Message Title javipolo created an issue Puppet / PUP-6446 Cant use 'master' or 'agent' as environment names Issue Type: Bug Affects Versions: PUP 3.8.7 Assignee: Unassigned Components: Puppet Server Created: 2016/06/27 10:25 AM Environment: linux, debian jessie Priority: Normal Reporter: javipolo When using an environment named master, agent or main, it does not work Here I show having 2 environments named production and master When I get modulepath for production expansion is correctly done and everything works fine, but when I try to get it for master environment, it just prints the default basemodulepath
