17.02 Release Notes

The 17.02 release continues to expand BotFactory support, offers numerous UI and performance improvements as well as several bug fixes. Listed below are the release notes.

Release Highlights

  • Add scheduled events UI for managing scheduled events at scale
  • API activity logging is now stored in the database
  • Added support for harvesting AWS CloudWatch alarms
  • Added support for harvesting VPC flow logs
  • Global scope can now be assigned for roles
  • Add support for harvesting AWS RDS instance reservations

New Filters & Actions

  • Cloud Alarms: Identify service regions without cloud alarms
  • Cloud Alarms: Identify cloud accounts without cloud alarms
  • Cloud Alarms: Identify alarms which transition between states
  • Network Flow Logs: Network has flow logs enabled/disabled
  • Network Flow Logs: Network flow log is impaired
  • Network Flow Logs: Network flow log supports traffic type
  • Instance: Filter for identifying instances by the length of time in a particular state
  • Volumes: Action to modify the properties of an EBS Volume
  • Instances: Action to force the deletion of an AWS instance. This will workaround API termination protection. Exercise caution with this!
  • All Resources: Action to assign resource ownership
  • All Resources: Action to remove resource ownership

General Improvements

  • Improved resource navigation
  • Add AWS EBS volume modification support
  • Add resource count column for resources owned by user and provide direct linking
  • Resource type now included in the ResourceCommonData object
  • Two-factor login flow improved to mitigate end-user confusion
  • Add sorting capabilities to the Resource Noncompliance of a bot
  • Resource property panel now shows resource creation and discovered timestamps
  • Resource property panel now shows the name of the resource owner (if set)
  • On-demand jobs now have a default TTL of two hours
  • Internet Gateways now display as a dependency of networks
  • Assigning resource tags now leverages the scheduled event system
  • Added improved cache busting and minification across CSS and JS assets
  • Moved HTML partials out of bundle for faster application load times
  • Convert reserved instance filters to use multi-select
  • Add external ID support for AWS STS AssumeRole
  • Min/max CPU values are now harvested for AWS instances via CloudWatch
  • Improved add cloud documentation for GCE, Azure and OpenStack
  • Updated pricing data for EC2
  • Improved database efficiency for modified or deleted resources

Bug Fixes

  • Newly created bots now display both creation and modification times in UTC
  • Badges belonging to orphaned/deleted resources are now properly pruned
  • Properly reset pagination controls when transitioning between resource types in resource noncompliance
  • Organization SMTP settings can now saved with empty credentials
  • Removed md-cell directive from a number of tables which degraded UI performance
  • Fixed harvesting related to RDS, memcache, elasticache, and redshift for AWS account numbers that begin with zeroes
  • Fixed an issue with displaying the type of an AWS database instance
  • Bot filter Clouds With No Service Users now targets noncompliance on the correct branch
  • Fixed typos in compute, memcache and database instance audit bots which resulted in download issues via GitHub

Developer/Administrator Notes

  • In an effort to normalize resource creation time a new column has been added to the Instance database object: create_time. This is a timestamp column as opposed to the launch_time counterpart which was a string. We will be deprecating launch_time in favor of this new column in 17.04. Accessing the old column will result in a deprecation warning informing developers to update their code.
  • Bot creation/modification via the API no longer requires transforming the instruction set. This means that developers can adhere to the standard data model supplied when listing bots.
  • There have been API changes for several blueprint calls throughout the stack. The calls listed below have had their supported HTTP method changed from POST to either DELETE or GET.
/v2/public/bot_templates/bot_templates/list', methods=['GET']
/v2/public/bot_templates/bot_templates/<template_id>/get', methods=['GET']
/v2/public/bot_templates/bot_templates/<template_id>/delete', methods=['DELETE']
/v2/public/cloudtypes/list', methods=['GET']
/v2/public/clouds/list', methods=['GET']
/v2/public/cloud/<resource_id_str>/regions/list', methods=['GET']
/v2/public/resourcegroups/system/list', methods=['GET']
/v2/public/resourcegroups/list', methods=['GET']
/v2/public/resource/<resource_id_str>/detail', methods=['GET']
/v2/public/resource/<resource_id_str>/tags/list', methods=['GET']
/v2/public/serviceuser/<serviceuser_resource_id_str>/delete', methods=['DELETE']
/v2/public/users/list', methods=['GET']
/v2/public/user/info', methods=['GET']
/v2/prototype/authenticationserver/<authentication_server_id_str>/delete', methods=['DELETE']
/v2/prototype/database/<instance_resource_id_str>/delete', methods=['DELETE']
/v2/prototype/diagnostics/queues/status/get', methods=['GET']
/v2/prototype/domain/organizations/get', methods=['GET']
/v2/prototype/domain/organization/<resource_id_str>/delete', methods=['DELETE']
/v2/prototype/domain/organization/<resource_id_str>/email/settings', methods=['GET']
/v2/prototype/domain/admin/<resource_id_str>/delete', methods=['DELETE']
/v2/prototype/groups/list', methods=['GET']
/v2/prototype/group/<resource_id_str>/delete', methods=['DELETE']
/v2/prototype/provisioning_templates/list', methods=['GET']
/v2/prototype/reports', methods=['GET']
/v2/prototype/reports/<report_id>/get', methods=['GET']
/v2/prototype/resource/<resource_id_str>/delete', methods=['DELETE']
/v2/prototype/resource/<resource_id_str>/supported_actions/get', methods=['GET']
/v2/prototype/system/settings/list', methods=['GET']
/v2/prototype/user/<user_id_str>/delete', methods=['DELETE']