Open qupig opened 5 months ago
That file is a sample file that's not intended to be used directly until it's modified.
For booleans, it shows both options.
This would normally be generated by hand based on the info in the template docs.
Someone built an addon to do this as well
https://addons.mozilla.org/en-US/firefox/addon/enterprise-policy-generator/
That file is a sample file that's not intended to be used directly until it's modified. For booleans, it shows both options.
Yes, I know, that takes a lot of conversion, and I've noticed some errors.
This would normally be generated by hand based on the info in the template docs.
Oh, and thanks for the work you put into this, it would be nice to have some automated processes.
https://addons.mozilla.org/en-US/firefox/addon/enterprise-policy-generator/
Good to know, I checked out the project and it produces some meta data policies.js
, that's nice, but it seems the project stopped being updated about 4 years ago?
I was just thinking about something simple that would be helpful for this project, maybe just some cli utils.
By the way, I just performed some simple transformations on it (unfinished):
So you're thinking this would be a separate file in github?
So you're thinking this would be a separate file in github?
I don't know. What do you think? If that helps people use the repo and get continued updates, why not?
But more importantly, I don't want anyone to increase their workload by maintaining this file individually.
So I'd like to have a set of source data there for generating these types, demo templates, or even the documentation.
Essentially I hope to reduce the workload of this repo and make it more usable by people.
It's not that easy to create anything useful from a document, and it's easy to make mistakes by repeating templates by hand.
Specifically, I might want create a generator similar to the project below that generates the required file types from upstream source data and is sustainably maintained.
Making an external project or extension may be easy, but keeping it up to date with upstream is not easy unless we embed it into a CI/CD workflow.
So it looks like the required upstream source data is at: policies-schema.json
I love this idea. Policies-schema.json definitely has all the information we need in it.
I'll support you however I can.
Right now my release work is very manual and anything I could automate would be great.
I would like to do this by writing the policies template with type checking in a JavaScript file and then generating the
policies.json
ororg.mozilla.firefox.plist
file directly. (I'm not familiar with Windows Group Policy, but maybe it works as well.)Type checking helps us write correct template object, or can be used to build front-end GUI interfaces.
The
json
andplist
conversion can be easily done usingplutil
that comes with macOS:I've tried using this example
policies.json
to write the Types definition.But what I'm interested in is, how is this file generated?
It's not a legal
JSON
file, but more like an interface defined inTypeScript
, except it uses some actual strings as examples.Is there already a hidden project used to generate the example files that already contains those Type definitions?
Or would the project be interested in receiving contributions to add Type definitions and/or conversion tools?
I just hope that we don’t reinvent the wheel, or that creating a wheel can help more developers/users with the same needs.