"title"=>"March 13, 2024",
"summary"=>nil,
"content"=>"AlloyDB for PostgreSQL\n
Feature
\nAlloyDB now supports continuous backup and recovery, and scheduled backups on secondary clusters. When you create a secondary cluster, any backup plans on the primary cluster are automatically copied to the new secondary cluster. For more information, see About cross-region replication.
\nAnti Money Laundering AI\nAnnouncement
\nReleased a new v4 engine versions for the commercial line of business, with more reliable tuning performance, in particular for small datasets.
\nApigee X\nAnnouncement
\nAs of March 13, 2024, the conversion of Apigee API Management organizations with Pay-as-you-go pricing provisioned before October 1, 2023, to Pay-as-you-go organizations that use updated attributes for pricing is complete, with the exception of one organization that requires customer action.
\n\nThe Apigee API Analytics add-on is enabled in converted organizations.The Analytics add-on can be disabled if it is not required. In addition, you can update your Pay-as-you-go environment types using the API.
\n\nFor more information on the updated pricing and enhanced features now available for these organizations, see Pay-as-you-go (updated attributes) overview.
\n\nUpdated pricing attributes will be reflected in March invoices. For billing questions related to this change, contact Google Cloud Billing support.
\nChronicle SOAR\nAnnouncement
\nRelease 6.2.51 is currently in Preview.
\nFeature
\nJobs Enhancement
\n\nWhen updating an integration, the jobs will now be updated automatically.\nThis does not apply to any legacy jobs that were created before October 2023.
\n\nThe Marketplace integration will clearly identify the legacy jobs that are affected and provide instructions on how to proceed.
\n\nIn addition, legacy jobs are now marked as such in the Jobs Scheduler page so that you can take action and resolve issues beforehand.
\nChanged
\nAPIs now documented
\n\nThe following APIs are not new, but with this Release are now formally documented in Swagger:
\n\nAddOrUpdateEnvironmentRecords
\n\nRemoveEnvironmentRecords
\nFixed
\nSearching for cases from the last week doesn't produce results (ID #00269819)
\nFixed
\nEmail HTML Templates > Show Email Template not rendering styles (ID #00249556)
\nFixed
\nSDK call for create entity failure displays the wrong error message (ID #48950075)
\nCloud Billing\nFeature
\nYou can now view granular Bigtable usage in the Cloud Billing Detailed export to BigQuery
\n\nYou can now view granular Bigtable instance cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your detailed Bigtable instance usage.
Review the schema of the Detailed cost data export.
\nFeature
\nYou can now view granular Memorystore for Redis usage in the Cloud Billing Detailed export to BigQuery
\n\nYou can now view granular Memorystore for Redis cost data in the Google Cloud Billing detailed export. Use the resource.global_name and resource.name fields in the export to view and filter your detailed Memorystore for Redis usage.
Review the schema of the Detailed cost data export.
\nCloud Composer\nDeprecated
\nAll preview versions of Cloud Composer 2 are past their security notifications end date and are not supported. If your environment uses a preview version of Cloud Composer 2, then please upgrade this environment to a supported version or re-create it using the latest version of Cloud Composer 2.
\nIssue
\nIf you see frequent scheduler restarts in your Airflow 2.6.3 environment and the [scheduler]job_heartbeat_sec Airflow configuration option is set to a non-default value, you can fix this issue either by upgrading to Cloud Composer version 2.6.4 or by removing this option's override, so that it uses the default value.
Feature
\nCloud SQL now supports SQL Server Reporting Services (SSRS) on your instances. For more information, see Use SSRS for creating reports.
\nCompute Engine\nFeature
\nGenerally available: You can use SSH-in-browser to connect to TPU VMs. For more information, see Connecting to a Cloud TPU.
\nDataform\nAnnouncement
\nThe 3.0.0-beta.0 version of the open-source Dataform framework is available. This update introduces significant changes, including, but not limited to, the following:
\n\n- \n
- Deprecation of
dataform.jsonin favor ofworkflow_settings.yaml\n - Stateless package installation by
@dataform/cli\n - Warehouse-agnostic compilation output \n
You don't need to take immediate action to update your Dataform code.
\n\nFor more information, see the 3.0.0-beta.0 release on GitHub.
\nLooker\nAnnouncement
\nLooker 24.4 includes the following changes, features, and fixes.
\n\nExpected Looker (original) deployment start: Monday, March 18, 2024
\n\nExpected Looker (original) final deployment and download available: Thursday, March 28, 2024
\n\nExpected Looker (Google Cloud core) deployment start: Monday, March 18, 2024
\n\nExpected Looker (Google Cloud core) final deployment: Monday, April 1, 2024
\nBreaking
\nQuery IDs can no longer be used to fetch queries or create render tasks through the API. The Get All Running Queries API endpoint is now restricted to admins only. Query slugs that are generated by Looker will be 32 characters instead of 7.
\nBreaking
\nChrome is starting to deprecate third-party cookies as of January 2024. Because of Looker's dependency on third-party cookies to establish embed user sessions, this may impact your embed use case. For more information, see the Chrome is deprecating third-party cookies notice.
\nBreaking
\nPreviously, custom visualizations would not call the updateAsync function after the vis config is updated via the custom visualization API. Now, the function will be called. If a custom visualization is set up to update the vis config every time updateAsync is called, it could cause excessive refreshes.
If your custom visualization is fails to load after this update, double check your custom visualization code for unnecessary vis config updates. If you have a Looker (original) instance, you can also enable the Custom Vis Reliable Render Labs feature which causes Looker to suppress excess refresh behavior in custom visualizations.
\nFeature
\nThe Performant Field Picker feature is now generally available.
\nFeature
\nWhen an instance has no projects, Looker will more prominently prompt users to create a model.
\nFeature
\nIn the Create a model wizard, your selections are now saved even if you close steps without having completed the model creation process.
\nFeature
\nAdding a query slug to source queries in the merge query API response GET merge_queries/<merge_query_id> returns the query slug in addition to the ID.
Feature
\nThe save_content permission now has two child permissions, save_dashboards and save_looks. These permissions let Looker admins exert finer control over the kinds of content that users can save.
Fixed
\nOnly users who have access to dashboard extensions will be shown the Add Extension tile.
\nFixed
\nSubtotals have been fixed for queries with order_by_field references in query streaming pathways. This feature now performs as expected.
Fixed
\nAn issue where embed secrets might have been visible to non-admin users has been fixed. This feature now performs as expected.
\nFixed
\nLooker now ignores all blank filter strings, including IS NOT.
Fixed
\nAn issue has been fixed that caused small decimals to be displayed in scientific notation even when formatting was disabled. This feature now performs as expected.
\nFixed
\nAn issue has been fixed where the PDT Context Override toggle was improperly reflecting the ON state when it had been cleared prior. This feature now performs as expected.
\nFixed
\nPerformant field picker sorting behavior has been fixed. This feature now performs as expected.
\nFixed
\nDownloading results from SQL Runner now only downloads the file and does not open the file in a new browser tab.
\nFixed
\nFilter expressions including user attributes and OR logical conditions were being incorrectly populated when generating SQL. This feature now performs as expected.
\nFixed
\nA change in the Snowflake dialect was ported to Kotlin to maintain parity. Snowflake column names with mixed cases are now properly quoted.
\nFixed
\nFilter suggestion requests have been reduced while the user is typing. Because normal typing will invoke fewer requests, the load on the server will be reduced.
\nFixed
\nAn issue that caused single value change indicators to not render in Safari when dashboards scrolled has been fixed. This feature now performs as expected.
\nFixed
\nThe LookML Validator no longer hangs on a connection that references a deleted or malformed user attribute. The Validator also surfaces a detailed error when the user tests the connection.
\nFixed
\nAn issue has been fixed where extension documents would appear when hiding Looker document links was disabled. This feature now performs as expected.
\nFixed
\nContent Validator has added support for field replacement within custom measure filters (across Looks, dashboard elements, and merge queries).
\nFixed
\nQueries with order_by_field references and subtotals should render correctly in downloads / run_query APIs.
Fixed
\nLooker should now correctly handle cases where the sorts query had an empty string or was entirely empty.
\nFixed
\nPreviously, the All Results option was unavailable for schedules on Looks. This feature now performs as expected.
\nFixed
\nOn the new Admin - Users page, Looker Support users were shown as having never logged in even for currently logged-in users. This issue has been fixed and this feature now performs as expected.
\nFixed
\nLookML-defined fields that are used in field filters will not be rejected from a set when the field requiring them is rejected from that set. This feature now performs as expected.
\nFixed
\nPreviously, the Errors and Broken Content dashboard appeared twice in the admin panel. This feature now performs as expected.
\nFixed
\nA data validation message is now returned for waterfall charts when there are multiple measures and a hidden dimension.
\nFixed
\nLooker now shows a clearer warning message when a user attempts to download a query with dimension fill and All Results enabled.
\nFixed
\nLooker no longer imposes the Explore row limit of 5,000 on queries that are run using the run inline query API endpoint.
\nFixed
\nPreviously, the lookml_model_explore API endpoint would return a 500 error in certain cases. This feature now performs as expected.
\nFixed
\nErrors about UI downloads are now more descriptive, similar to descriptive API error messages.
\nFixed
\nInternal encryption has been migrated from AES-128 to AES-GCM-256 encryption.
\nFeature
\nThe Disallow Numeric Query IDs legacy feature has been added to let users opt in to or out of query API changes.
\nFeature
\nThe Advanced Features for New Schedules Page Labs feature is now available. This lets you sort and filter the list of scheduled plans on the Admin - Schedules page.
\nFixed
\nPreviously, when a dashboard was scheduled using PNG format and one of the tiles contained an empty note, the schedule would fail. This feature now works as expected.
\nFixed
\nThe Export function has been re-enabled, which lets Looker admins export data from a Looker (original) instance for import into a Looker (Google Cloud core) instance.
\nFixed
\nIncorrect quoting in Snowflake views has been fixed.
\nFixed
\nIAM checks for ephemeral users were disabled as a result of rendering issues for users who were logged in with SAML in Looker (Google Cloud core).
\nResource Manager\nFeature
\nYou can add tags at the time of creating folders and projects. These tags can be added as key-value pairs. For more information, see Add tags during folder creation and Add tags during project creation. This feature is currently in preview.
\nStorage Transfer Service\nFeature
\nSupport for transfers from cloud and on-premises Hadoop Distributed File System (HDFS) sources is now generally available (GA).
\n\nHDFS support allows for use cases such as migrating from on-premises storage to Cloud Storage, archiving data to free up on-premises storage space, replicating data to Google Cloud for business continuity, or transferring data to Google Cloud for analysis and processing.
\n\nSee Transfer from HDFS to Cloud Storage for details.
\n\n ","author"=>nil,
"link"=>"https://cloud.google.com/release-notes#March_13_2024",
"published_date"=>Wed, 13 Mar 2024 07:00:00.000000000 UTC +00:00,
"image_url"=>nil,
"feed_url"=>"https://cloud.google.com/release-notes#March_13_2024",
"language"=>nil,
"active"=>true,
"ricc_source"=>"feedjira::v1",
"created_at"=>Sun, 31 Mar 2024 21:42:30.261988000 UTC +00:00,
"updated_at"=>Mon, 13 May 2024 18:39:40.536905000 UTC +00:00,
"newspaper"=>"GCP latest releases",
"macro_region"=>"Technology"}