Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Product Compatibility

Refer to product compatibility to determine supported Operating Systems and Database Versions.

...

Status
subtletrue
colourGreen
titleDRAFT RELEASED
?? 30 August 2023

New release with improvements and bug-fixes.

Improvements

  • New feature: When the compliance system generates an exception it should generate an event.
  • Fix issue when deleting entry in command set re-appears after saving in opConfig.
  • Fix issue when a change is made in a node configuration, NMIS detects it and raise an event with title  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.

Bug Fixes

  • Fix deleting an entry in a Command Set would reappear after saving.
  • Fix Command change detection so that opConfig raises an event with title "Node Configuration Change Detected".
  • Fix issue when we try to add adding schedule for config set Config Set from Schedule Configuration Changes screen, it does not create a schedulenow creates a schedule.
  • Fix pre and post commands disappearing when a Config Set is saved.
  • Fix Command Output screen where the  'Run Command Now' button didn't work when screen width was reduced.

opConfig 4.5.1

Status
subtletrue
colourGreen
titleReleased
02 January 2023

...

  • 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_revisionfor 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:

...

Code Block
     "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:

...

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:

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"

...

  • opConfig installer checks and sets opconfig_raise_alert_events and opconfig_raise_change_events. 
  • Added security content header. This is affecting all the products. The content security policy can be overwritten using the configuration item "security_content_policy".
  • Removed cron line with action import_audit. 
  • Added AIX phrasebook.

Bug Fixes

  • Connection errors are not saved as command revisions.
  • Command collection was not run if no nodes were specified. This may prevent some cron tasks to run. Now, If no nodes are specified, the command will run for all nodes. 
  • Considered just local nodes for license check. 
  • Fixed "Can't call method node on an undefined value" error in some command outputs.
  • Now it is possible to install opConfig on an alternative path using -t.
  • Connect options was not working. 

...

Status
subtletrue
colourGreen
titleReleased
25 May 2021

Bug Fixes

  • Fixed issue in opConfig where a large amount MongoDB connections were created and retained.

...

  • Command Set Parameters
    • opConfig now supports parameterized command sets. Eg: ping $ipaddress
    • Parameters can be passed in via the command line. Eg parameters.x
    • When creating a new Virtual Operator Job, if you have selected a command set which has parameters, the form will then display "Next" and the second screen will ask you to provide parameters
    • Parameters can also be passed in through derived data
    • Parameters currently have two data types, "string" and "ipaddress"
      • ipaddress is just used for front end validation, the cli does no validation
    • parameters_required => "true" can be set. If the parameters from the cli or gui have not been passed in, opConfig will not run the command
    • Parameters get defined by a top level key and are an array of objects with two keys: parameter and type

      Code Block
      "parameters" : [
               {
                  "parameter" : "id",
                  "type" : "String"
               },
               {
                  "type" : "String",
                  "parameter" : "name"
               }
            ],


  • Command Set Editor under "System" > "Manage Command Sets"
    • You can delete, update and create new command sets through a visual GUI
    • Only command sets under conf/command_sets.d/ can be modified.
  • Derived Data has new types of table columns to display related jobs or create new virtual operator jobs from. Plugins in opConfig#NewDerivedInformationElementsinopConfig4.2.1
  • Conditions has new types of table columns to display tags, urls and tooltips, More details can be found here Plugins in opConfig#NewReportConditionElementsinopConfig4.2.1
  • New top level key, "active" can be set to "true"/"false" if false the command set wont be loaded
  • New key for commands "active" can be set to "true"/"false" if false the command from that set wont be loaded, other commands set to true will be loaded as part of the set.


BugFixes

  • Fixed issue where opConfig would report duplicate command sets.
  • Fixed Issue where the trouble shooting button would always display.
  • Fixed issue with logging at debug levels not requested in opconfig-cli
  • Fixed issue where opcharts-cli would not honor different debug levels

...