Product Compatibility

...

• Compliance Report Enhancements
  • The Compliance
  report
  • Report now includes only opConfig
  active
  • activated nodes when generating the final report.
  • This ensures that only currently
  active
  • activated nodes are considered, providing more accurate and relevant compliance data.
• Automated Purging of old Compliance Reports

  • A new

  purging job

  • command-line script has been

  added to automatically delete

  • introduced to automate the deletion of compliance report outputs that are older than a specified number of days.

  • The script can be executed using the following command:
  • ./opconfig-cli.pl act="purge_compliance_output" purge_older_than=23
  • This example command will remove all compliance outputs older than 23 days.
  • This helps in managing storage efficiently and ensures that only recent compliance data is retained.

opConfig 4.6.0

...

New release with improvements and bug-fixes.

Improvements

• When the compliance system generates an exception it generates an event.
• Added option print_command_output=true  for opConfig CLI config command sets.
• Automatically apply OS detection.  For example, if we know a node is Linux, run some commands to determine if it is Debian, Ubuntu, CentOS, etc.

...

• Improved mongodb index for command sets.
• Improved the "Help screen" for Command Sets and Config Sets
• Added the "Discover OS Info", "Discover Connection Details" and "Test Connection" buttons for nodes in opAdmin
• New CRUD API for credential sets. 
• New CLI API for credential sets. 
• Improved main dashboard load times.
• Fix to protect a command.
• New parameter to increase the time out for a plugin per command set: 

  interaction_timeout

opConfig 4.3.1

16 Dec 2021

• Fix issue where using opConfig in classic auth node would show nodes you shouldn't have access to.
• Fix issue where virtual operator would break in classic auth mode.
• Fix issue where scheduling jobs would save the time using the browers timezone not the servers
• New improvement with a new parameter, compare_to_previous_revision, for config sets to avoid compare revisions. This parameter is specially helpful when the are big files to compare and the config sets are taking a really long time:

...

     "commands" : [
         {
            "privileged" : "true",
            "multipage" : "true",
            "compare_to_previous_revision" : "false",
            "use_processing_plugins" : [
               ""
            ],
            "report_level_min_changes" : null,
            "active" : "true",
            "tags" : [
               "application",
               "troubleshooting"
            ],
            "use_collection_plugin" : "",
            "command" : "scp my/file"
         },

opConfig 4.3.0

1 Dec 2021

RELEASED 

• Updated core dependencies
• Cookies now support samesite strict, see Security Configurations
• Fixed issue in checkdaemons.sh with stopping monogdb

opConfig 4.2.7

26 Oct 2021

RELEASED 

This release includes:

• Spanish translations.

opConfig 4.2.6

21 Sept 2021

RELEASED 

This release includes the following new features:

...

• Now is possible to use phrasebook macros in Command Sets.
• GUI improvements.

opConfig 4.2.5

10 Aug 2021

RELEASED Bug fixes

• Fixed issue where editing a node in opConfig would overwrite the nodes configuration
• Test connection error now shows the current error state and if the node name cannot be found it will use the nodes uuid
• Installer now changes the config option opconfig_default_period from 8d to 2d

opConfig 4.2.4

RELEASED 30 Jul 2021

This release includes:

• Security updates. More information in the following link. 
• Migration script utility: To migrate the connection info and OS info node data when upgrading from opConfig 3. 

opConfig 4.2.3-1

RELEASED 29 Jul 2021

Bug Fix

• Fixes an issue in ./omk/conf/opCommon.json and ./omk/install/opCommon.json by changing the following entry:
  • "omk_show_getting_started_widgets" : true
    becomes
    "omk_show_getting_started_widgets" : "true"

...