@turbot/azure-frontdoorservice
Recommended Version
Version
5.7.0
Released On
Nov 20, 2023
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 > Front Door > Front Door > Active
- Azure > Front Door > Front Door > Approved
- Azure > Front Door > Front Door > CMDB
- Azure > Front Door > Front Door > Discovery
Policy Types
- Azure > Front Door > Enabled
- Azure > Front Door > Front Door > Active
- Azure > Front Door > Front Door > Active > Age
- Azure > Front Door > Front Door > Active > Last Modified
- Azure > Front Door > Front Door > Approved
- Azure > Front Door > Front Door > Approved > Custom
- Azure > Front Door > Front Door > Approved > Usage
- Azure > Front Door > Front Door > CMDB
- Azure > Front Door > Permissions
- Azure > Front Door > Permissions > Levels
- Azure > Front Door > Permissions > Levels > Modifiers
- Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-frontdoorservice
- Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-frontdoorservice
Release Notes
5.7.0 (2023-11-20)
What's new?
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.
Policy Types
- Azure > Front Door > Front Door > Approved > Custom
5.6.0 (2021-07-16)
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.
Bug fixes
- We’ve made a few improvements in the GraphQL queries for various controls, policies, and actions. You won’t notice any difference, but things should run lighter and quicker than before.
5.5.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.5.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.4.0 (2020-09-26)
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.3.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.
5.2.2 (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.2.1 (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.
5.2.0 (2020-05-27)
Warning
- The
Azure > Front Door > Permissions
policy valueEnabled if Azure > FrontDoor > Enabled
has been deprecated and will be removed in v6.0.0. The policy's default value will also be changed toEnabled if Azure > Front Door > Enabled
. Any policy settings using the deprecated value should be updated to useEnabled if Azure > Front Door > Enabled
instead before installing the next major version.
Resource Types
Renamed
- Azure > Front Door Service to Azure > Front Door
- Azure > Front Door Service > Front Door to Azure > Front Door > Front Door
Control Types
Renamed
- Azure > Front Door Service > Front Door > Active to Azure > Front Door > Front Door > Active
- Azure > Front Door Service > Front Door > Approved to Azure > Front Door > Front Door > Approved
- Azure > Front Door Service > Front Door > CMDB to Azure > Front Door > Front Door > CMDB
- Azure > Front Door Service > Front Door > Discovery to Azure > Front Door > Front Door > Discovery
Policy Types
Renamed
- Azure > Front Door Service > Enabled to Azure > Front Door > Enabled
- Azure > Front Door Service > Front Door > Active to Azure > Front Door > Front Door > Active
- Azure > Front Door Service > Front Door > Active > Age to Azure > Front Door > Front Door > Active > Age
- Azure > Front Door Service > Front Door > Active > Last Modified to Azure > Front Door > Front Door > Active > Last Modified
- Azure > Front Door Service > Front Door > Approved to Azure > Front Door > Front Door > Approved
- Azure > Front Door Service > Front Door > Approved > Usage to Azure > Front Door > Front Door > Approved > Usage
- Azure > Front Door Service > Front Door > CMDB to Azure > Front Door > Front Door > CMDB
- Azure > Front Door Service > Permissions to Azure > Front Door > Permissions
- Azure > Front Door Service > Permissions > Levels to Azure > Front Door > Permissions > Levels
- Azure > Front Door Service > Permissions > Levels > Modifiers to Azure > Front Door > Permissions > Levels > Modifiers
Action Types
Renamed
- Azure > Front Door Service > Front Door > Delete to Azure > Front Door > Front Door > Delete
- Azure > Front Door Service > Front Door > Router to Azure > Front Door > Front Door > Router
5.1.1 (2020-05-19)
Bug fixes
- Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.
Policy Types
Renamed
- Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-frontdoor to Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-frontdoorservice
- Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-frontdoor to Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-frontdoorservice