8000 User-specific ~/.boxen/config.json not loaded · Issue #193 · boxen/boxen · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on May 22, 2018. It is now read-only.

User-specific ~/.boxen/config.json not loaded #193

Open
aaronlerch opened this issue Sep 30, 2015 · 4 comments
Open

User-specific ~/.boxen/config.json not loaded #193

aaronlerch opened this issue Sep 30, 2015 · 4 comments

Comments

@aaronlerch
Copy link

I'm still investigating this, and don't have a clean repro out there, but I'm at the point where I'm comfortable opening an issue in the hopes that someone more experienced can quickly tell me I'm crazy or that I'm on to something.

Using v2.7.2, I am seeing that facts we have specified in ~/.boxen/config.json are not getting parsed & loaded.

My config.json looks like this:

{"bitbucket_user":"aaronlerch"}

We reference $::bitbucket_user in various places in our personal, project, and team manifests.

After some updates, this value has now been empty where before it contained the correct config.json-specified value.

The behavior I am seeing is that the manifest is now being processed as root so in lib/facter/boxen.rb the line dot_boxen = "#{ENV['HOME']}/.boxen" looks for (on my mac) /var/root/.boxen/config.json.

I suspect that this commit might have broken user-specific config.json support: 11bf1f0

Puppeteer is running everything via sudo which I believe explains this behavior.

So it seems that config.json support has been broken for a while? Or am I way off on my analysis here?

Thanks!
Aaron
@aaronlerch
Copy link
Author

Well it's clear to me now that the commit I referenced is not related, I just got a bit confused.

But I'm still every confused as to why things haven't seemed to change, but now when puppet is run via sudo (as it seems to have been for a very long time) it doesn't keep the environment from the invoking process. If that's indeed what it used to do?

@rgabo
Copy link
rgabo commented Oct 18, 2015

@aaronlerch, we're seeing the same issue and I've spent a couple hours to investigate where the code is failing to pick up config.json to no avail.

Were you able to figure out what is going on?

@aaronlerch
Copy link
Author

@rgabo unfortunately I wasn't able to figure it out and I just mitigated it by changing how our user-specific settings were specified. the problem is that boxen is reading this file as root and not as a user, so it tries to pull it from the root user home directory. I wasn't able to figure out why it is doing this. :(

@rgabo
Copy link
rgabo commented Oct 22, 2015

@aaronlerch thanks for the answer, I guess we'll then centralize the user-specific settings for the time being. Not the most ideal, I'll let you know if we find another way.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aaronlerch @rgabo
0