@turbot/azure-mysql
Recommended Version
Version
5.10.0
Released On
Apr 19, 2024
Depends On
@turbot/azure ^5.0.0
@turbot/azure-iam ^5.0.0
@turbot/azure-provider ^5.0.0
@turbot/turbot ^5.22.0
@turbot/turbot-iam ^5.1.0
@turbot/azure-iam ^5.0.0
@turbot/azure-provider ^5.0.0
@turbot/turbot ^5.22.0
@turbot/turbot-iam ^5.1.0
Resource Types
Control Types
- Azure > MySQL > Flexible Server > Active
- Azure > MySQL > Flexible Server > Approved
- Azure > MySQL > Flexible Server > CMDB
- Azure > MySQL > Flexible Server > Discovery
- Azure > MySQL > Flexible Server > Encryption in Transit
- Azure > MySQL > Flexible Server > Minimum TLS Version
- Azure > MySQL > Flexible Server > Tags
- Azure > MySQL > Server > Active
- Azure > MySQL > Server > Approved
- Azure > MySQL > Server > CMDB
- Azure > MySQL > Server > Discovery
- Azure > MySQL > Server > Encryption in Transit
- Azure > MySQL > Server > Tags
Policy Types
- Azure > MySQL > Approved Regions [Default]
- Azure > MySQL > Enabled
- Azure > MySQL > Flexible Server > Active
- Azure > MySQL > Flexible Server > Active > Age
- Azure > MySQL > Flexible Server > Active > Last Modified
- Azure > MySQL > Flexible Server > Approved
- Azure > MySQL > Flexible Server > Approved > Custom
- Azure > MySQL > Flexible Server > Approved > Regions
- Azure > MySQL > Flexible Server > Approved > Usage
- Azure > MySQL > Flexible Server > CMDB
- Azure > MySQL > Flexible Server > Encryption in Transit
- Azure > MySQL > Flexible Server > Minimum TLS Version
- Azure > MySQL > Flexible Server > Regions
- Azure > MySQL > Flexible Server > Tags
- Azure > MySQL > Flexible Server > Tags > Template
- Azure > MySQL > Permissions
- Azure > MySQL > Permissions > Levels
- Azure > MySQL > Permissions > Levels > Modifiers
- Azure > MySQL > Regions
- Azure > MySQL > Server > Active
- Azure > MySQL > Server > Active > Age
- Azure > MySQL > Server > Active > Last Modified
- Azure > MySQL > Server > Approved
- Azure > MySQL > Server > Approved > Custom
- Azure > MySQL > Server > Approved > Regions
- Azure > MySQL > Server > Approved > Usage
- Azure > MySQL > Server > CMDB
- Azure > MySQL > Server > Encryption in Transit
- Azure > MySQL > Server > Regions
- Azure > MySQL > Server > Tags
- Azure > MySQL > Server > Tags > Template
- Azure > MySQL > Tags Template [Default]
- Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-mysql
- Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-mysql
Release Notes
5.10.0 (2024-04-19)
What's new?
You can now configure Encryption in Transit for Flexi Servers. To get started, set the
Azure > MySQL > Flexible Server > Encryption in Transit > *
policies.We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.
Resource's metadata will now also include
createdBy
details in Turbot CMDB.
Control Types
- Azure > MySQL > Flexible Server > Encryption in Transit
Policy Types
- Azure > MySQL > Flexible Server > Encryption in Transit
Action Types
- Azure > MySQL > Flexible Server > Update Encryption in Transit
5.9.0 (2024-04-08)
What's new?
- You can now configure TLS version for Flexi Servers. To get started, set the
Azure > MySQL > Flexible Server > Minimum TLS Version > *
policies.
Control Types
- Azure > MySQL > Flexible Server > Minimum TLS Version
Policy Types
- Azure > MySQL > Flexible Server > Minimum TLS Version
Action Types
- Azure > MySQL > Flexible Server > Set Minimum TLS Version
5.8.0 (2024-04-01)
What's new?
- TLS version and audit log details will now be available in CMDB for Flexi Servers.
5.7.0 (2023-05-19)
What's new?
- Users can now create their own custom checks against resource attributes in the Approved control using the
Approved > Custom
policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.
Resource Types
- Azure > MySQL > Flexible Server
Control Types
- Azure > MySQL > Flexible Server > Active
- Azure > MySQL > Flexible Server > Approved
- Azure > MySQL > Flexible Server > CMDB
- Azure > MySQL > Flexible Server > Discovery
- Azure > MySQL > Flexible Server > Tags
Policy Types
- Azure > MySQL > Flexible Server > Active
- Azure > MySQL > Flexible Server > Active > Age
- Azure > MySQL > Flexible Server > Active > Last Modified
- Azure > MySQL > Flexible Server > Approved
- Azure > MySQL > Flexible Server > Approved > Custom
- Azure > MySQL > Flexible Server > Approved > Regions
- Azure > MySQL > Flexible Server > Approved > Usage
- Azure > MySQL > Flexible Server > CMDB
- Azure > MySQL > Flexible Server > Regions
- Azure > MySQL > Flexible Server > Tags
- Azure > MySQL > Flexible Server > Tags > Template
- Azure > MySQL > Server > Approved > Custom
Action Types
- Azure > MySQL > Flexible Server > Delete
- Azure > MySQL > Flexible Server > Router
- Azure > MySQL > Flexible Server > Set Tags
5.6.0 (2021-11-10)
What's new?
- We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.
Bug fixes
- We've made a few improvements in the GraphQL queries for various router actions. You won't notice any difference, but things should run lighter and quicker than before.
5.5.0 (2021-05-31)
What's new?
- We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.
5.4.2 (2021-01-22)
Bug fixes
- Controls run faster now when in the
tbd
andskipped
states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when intbd
andskipped
, resulting in faster and lighter control runs.
5.4.1 (2020-11-03)
Bug fixes
- We've updated the Discovery controls for resources to now move to skipped instead of invalid if the provider is disabled in the subscription and the
Azure > Provider > {service} > Registered
policy is checking if the provider is disabled. This will reduce the amount of noisy controls that cannot be easily resolved without making changes to the provider.
5.4.0 (2020-10-22)
What's new?
- We've made improvements to how Approved controls interact with CMDB policies and controls for more reliable approved checks. Now, if a resource's CMDB policy is set to
Skip
, its Approved control will move toinvalid
to prevent the Approved control from making a decision based on outdated information. Also, Approved controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.
5.3.0 (2020-09-28)
What's new?
- We've made improvements to how Active controls interact with CMDB policies and controls for more reliable active checks. Now, if a resource's CMDB policy is set to
Skip
, its Active control will move toinvalid
to prevent the Active control from making a decision based on outdated information. Also, Active controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.
5.2.0 (2020-08-26)
What's new?
- Discovery controls now have their own control category,
CMDB > Discovery
, to allow for easier filtering separately from other CMDB controls. - We've renamed the service's default regions policy from
Regions [Default]
toRegions
to be consistent with our other regions policies.
5.1.1 (2020-07-24)
Bug fixes
- When deleting inactive resources through an Active control, different warning periods in days can be set to delay deletion. We recently identified a bug that would cause these warning periods to be ignored, and any inactive resources would be deleted immediately. This bug has been fixed and now all Active controls will abide by the warning period set in the policy value.
5.1.0 (2020-06-03)
What's new?
- All resource Router actions now run even if Guardrails is outside of its allowed change window. This allows Guardrails to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Guardrails' ability to process resources changes that were made in the cloud provider - enforcement actions are still disabled outside of the change window.
Control Types
- Azure > MySQL > Server > Encryption in Transit
Policy Types
- Azure > MySQL > Server > Encryption in Transit
Action Types
- Azure > MySQL > Server > Update Encryption in Transit
5.0.2 (2020-05-12)
Bug fixes
- Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.