Skip to content

Feedloader v1.1.0
Compare
Choose a tag to compare
@starmandeluxe starmandeluxe released this 17 Mar 06:56
· 52 commits to main since this release
v1.1.0
bd6c670

To upgrade Feedloader to the latest version, it is required to run the install_to_gcp.sh script as well as push the latest code, .enc, and variables.json files to your Cloud Source Repository. See the README for details on how to install Feedloader.

New Features

Support for Local Inventory Ads ("LIA")

  • By setting the environment variable USE_LOCAL_INVENTORY_ADS to a boolean "True" value, Feedloader will now send all feed items to the "local" channel destination in Content API in addition to the "online" channel. See here for details on LIA.

    Note: Choosing to use this setting will make all of your products both "online" and "local".

Support for Excluded and Included Destinations

Bugfixes/Changes

Cloud Composer

  • Fixed a bug where the Cloud Composer Python dependencies and the updated version of Cloud Composer were incompatible. Updated these to ensure compatibility between the two.

  • Fixed a bug where instead of checking if Cloud Composer was already installed, the installation script will now remove any pre-existing Cloud Composer Feedloader instance before re-installing it. This is due to the fact that errors occur if a Cloud Composer upgrade is performed across versions.

Cloud Build

  • Deploying App Engine services has now been consolidated all into one build rule to ensure that GCP deploys these services in the required order.

Install-time Validation of Environment Variables

  • Added install-time validation of environment variables, specifically for EXPIRATION_THRESHOLD, TIMEZONE_UTC_OFFSET, USE_LOCAL_INVENTORY_ADS, IS_MCA, and SHOPTIMIZER_API_INTEGRATION_ON, since these variables are often unintentionally incorrectly set.

Documentation

  • Added a section on how to use the MCID-per-item feature.

  • Added a DevOps guide for maintainers of a Feedloader deployment with common operations and Frequently Asked Questions.

  • Added a section explaining that non-Feedloader installed/customized GCP components could interfere with deploy and normal operation of Feedloader if installed to a pre-existing customized GCP environment.

Assets 2
Loading