Vote please for distribution vehicle and formatting

https://bigfix-ideas.hcltechsw.com/ideas/BFPTCH-I-155

Add the ability to format relevance with indentation and new lines so it is easier to read.
Some relevancies can be long and complicated to follow if its all jammed together in one massive paragraph.

https://bigfix-ideas.hcltechsw.com/ideas/BFPTCH-I-156

When companies have > 1 bigfix instance (think 1 prod 1 dev or even more) and I develop a fixlet/task/baseline/analysis in a dev environment, how does one get the finished fixlet/task/baseline/analysis distributed to the other instances.

Let’s add a way in the bigfix console and webui, to be able to clone a fixlet/task/baseline/analysis from one bigfix environment to one or more other environments with the press of a button.

Different versions of bigfix would be supported only if the format of the content was acceptable to the target version, like sending v10 content to v9 system or v9 content to a v10 system.

1 Like

I don’t see it used very often, but it is actually acceptable to use format/spacing and even comments in relevance clauses - it’s only the Fixlet Debugger, on the QNA tab, that requires it to be a single line. The following is valid for a single fixlet relevance or analysis property, including comments delimit by /* and */

3 Likes

It would be nice to have a button called “Format” and it takes care of it for me.

1 Like

You do have formatting options in the “single clause” tab that can either indent the relevance or flatten it


image

1 Like

Fixlet debugger is great and all but not referring to that.

Imagine yourself editing relevance in the console or webui and a button is visible that says “Format Relevance”

Upon pressing it the code would do something similar to what jsonlint.com does when you throw a blob of json at it.

1 Like

Note that this (HCL Software - Sign In) does exist at least somewhat in the BigFix Console today:

That said, it would be good to add this to the WebUI, and also include the capability when creating content.

2 Likes

That format result is pretty weak. It could stand an overhaul.

Regarding the idea for a distribution vehicle, I like the idea submitted here:

https://bigfix-ideas.hcltechsw.com/ideas/BFPTCH-I-142

Having a Git repository back-end to BigFix would allow versioning of fixlets as you modify them, and also allow you to easily share fixlets between BigFix instances. You could also have different branches for different system versions, if needed.