Feature #27035
closed
Drop support for MySQL for both development and production environments
Added by Lukas Zapletal almost 6 years ago.
Updated over 3 years ago.
Description
Owner: lzap
The plan:
- announce on our blog that 1.25/2.0 will be the last release supporting MySQL
- implement a warning UI bar that MySQL is ending soon
- release 1.23 and 1.24 with tested documentation on how to migrate to MySQL
- remove MySQL from the installer
- remove MySQL packages
- drop MySQL from CI
- drop MySQL from docker image
- remove MySQL bundler group
would it be possible to offer a container that helps migrating data? something simple as
docker run foreman_mysql_migrator SOURCE=mysql://user:pass@mysql/foreman DST=pg://user:pass/pg/foreman
Rails can do the migration, see the blogpost. Can you explain what is the benefit of container approach?
- Related to Feature #27442: Issue notification for MySQL users about dropping support added
- Description updated (diff)
- Related to Bug #27589: Rake task to reset SQL sequences added
- Related to Refactor #27806: change docker-compose setup to use pg by default added
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7205 added
- Related to Refactor #28363: get rid of title_and_lookup_key_length validation in NestedAncestryCommon added
- Fixed in Releases 2.0.0 added
- Status changed from Ready For Testing to Closed
- Related to Refactor #28558: Remove mysql Puppet module from installer added
- Pull request https://github.com/theforeman/foreman/pull/8888 added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous