In order to tailor our development and CI environments to match BMO production, it would be useful to be able to see how they are configured based on the Puppet scripts. Currently, as i understand it, they are stored in SVN and we (BMO devs) do not have access to that. Thanks dkl
Do you guys need this access in git or should we wontfix?
I personally think it would still be useful. We can get notified when changes are made so that we can make sure our CI docker images are still mostly in sync with how production VMs are configured. dkl
It would be useful, although I think we've managed to reverse engineer it in docker-bmo-base to a sufficiently high degree. While I agree with dkl, I think I would say wontfix this because there are many other things I'd rather get out of ops :-)
reso/wontfix then, just to get it off our list
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
I talked with :digi and :cshields about this via email, and they've agreed to grant RO access with the following guidelines: - Avoid sharing with those who aren't given access. - Avoid snippets/diffs on public pastebins / bugs. For example, you'll have access to ldap_users and nagios (nagios has oncall phone numbers) which I think is technically PII, at least in the EU. :fubar, can we please add RO for the appropriate LDAP group?
Status: RESOLVED → REOPENED
Component: Legacy VCS → Git
Resolution: WONTFIX → ---
Done. To git-internal.mozilla.org:gitolite-admin.git 33e0396..c5a90d7 master -> master URL to clone is ssh://email@example.com/sysadmins/puppet.git
Assignee: nobody → klibby
Status: REOPENED → RESOLVED
Last Resolved: a year ago → a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.