We released version 1.1.0 of the Migrate to Containers modernization plugins

## Announcement On March 27, 2022 we released version 1.1.0 of the Migrate to Containers modernization plugins. Learn how to [Upgrade Migrate to Containers plugins](https://cloud.google.com/migrate/containers/docs/upgrade#upgrade%5Fplugins). ## Feature **Preview**: Added support for refactoring WordPress Servers running on Apache2 Linux to containers, which lets you deploy WordPress sites as containers on GKE, GKE Autopilot clusters, Anthos clusters, and Cloud Run. For more information, see [Migrate a WordPress site](https://cloud.google.com/migrate/containers/docs/migrating-overview#migrate%5Fa%5Fwordpress%5Fsite). ## Feature Introduced the following features for JBoss migration: * Support for JBoss versions has been extended and Migrate to Containers now supports migration of JBoss EAP versions 7.0 - 7.4 to equivalent Wildfly community based container images, besides migrations of Wildfly versions 8.1.0 - 26.1.1. * Secrets are now automatically created from extracted security realms configuration and key-stores. This new feature fixes potential security risks and lets you update secrets without having to recreate images. * The `targetImageHome` property has been added to the migration plan to allow users to specify an alternative container image with a different `JBOSS_HOME` location. * The `ExcludeFiles` property has been added to the migration plan, which lets you explicitly exclude files and directories from the container image. * The data migration feature now automates the creation and mounting of a Persistent Volume Claim (PVC) for the `$JBOSS_HOME/standalone/data` directory. This directory is available for use by services that require storing content in the file system. ## Fix Filtering out files located at `/tmp` when discovering Tomcat application dependencies. ## Issue Docker images may contain broken symlinks. Ensure that the tar archive artifacts added to dockerfile don't contain symlinks that don't resolve to another file in the archive. If they do, either retrieve the files from the source VM and add them to the dockerfile manually, or replace the symlinks in the source VM and perform extraction again.