Issue #6773 has been updated by Daniel Pittman.
Jay Flowers wrote:
> The registry can be useful but is by no mean where you are supposed to put
> configuration. The standard for a .Net application is to use a configuration
> file.
For the sort of information we are talking about here, it certainly used to be
the case that this was strongly discouraged; I can't find appropriate
documentation about modern policy. Is the UI now typically that users expect
to edit an XML configuration file? Are you referring to the the "MyApp.config"
style files installed with an EXE-hosted .net application?
> Management and reading of the config file has was made so easy in the first
> version on .Net that you almost always see it being used over the registry.
> I have no doubt the right thing to do here is continue with a configuration
> file. We just need to decide where to put it so that it is not a surprise,
> so that it meets with expectations of our users.
Do you know what standard Microsoft uses for locating them? Since they define
the platform, that is what matters. My reading of the current documentation is
that it depends on what we consider them, but you have more current experience
than I do, so:
On Unix we check system-wide if root, and per-user if not. I can't identify a
good distinction to draw on Windows along similar lines, but would think that
per-user is probably not the right choice. Would you agree?
I think that for the agent this is very much "configuration data", rather than
"documents", since the user has no interest in manipulating them like a
document; certainly, there would be no regular use like that, right?
That suggests to me that they live in the
"ProgramData\PuppetLabs\Puppet${Type}" namespace on Vista+, and the "All
Users\Application Data" namespace on XP. Does that seem reasonable?
When we come to the master, and the site manifests and modules, those seem like
per-machine "documents" and all. Does that seem reasonable?
----------------------------------------
Bug #6773: Install Script Fails; needs good default configdir for MS Windows
https://projects.puppetlabs.com/issues/6773
Author: Jay Flowers
Status: Accepted
Priority: High
Assignee:
Category: windows
Target version: 2.6.x
Affected Puppet version: 2.6.6
Keywords: windows install source
Branch:
When I run the install.rb script from source I get the following failure
message:
<pre>
C:\Projects\Puppet\puppet>ruby install.rb
Missing ronn; skipping man page creation
install.rb:92:in `mkdir': No such file or directory - /etc/puppet
(Errno::ENOENT)
from install.rb:92:in `do_configs'
from install.rb:492
</pre>
When I step through with the debugger it looks like this code might be what
needs to be addressed:
<pre>
265 if not InstallOptions.configdir.nil?
266 configdir = InstallOptions.configdir # <- This is not executed
267 else
268 configdir = "/etc/puppet" # <-This is executed
269 end
</pre>
I am not sure what is a good, or correct, value for a Widows platform
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
