task_manager

There are several ways to add that admin into the database:

1. rails console - Just open the console and execute AdminUser.create!(...).
2. seeds.rb - Open the db/seeds.rb file and paste AdminUser.create!(...). Then run rake db:seed. Note that running rake db:seed multiple times will create that admin multiple times - it's best you have some sort of validations or use AdminUser.find_or_create_by(...) instead.
3. rake task - create a rake file in lib/tasks, name is not important but it should end in .rake (ex: update.rake)

Change mongo = PyMongo(app) to

From to the Rails guides about Custom Rake tasks:

Custom rake tasks have a .rake extension and are placed in Rails.root/lib/tasks. You can create these custom rake tasks with the bin/rails generate task command.

That means your file should be named like this:

Should anyone get the same error in the future, here is what we were told by the AWS tech specialist:

There is a known (to AWS) issue with the pglogical plugin. The solution requires using the test_decoding plugin instead.

1. Enforce using the test_decoding plugin on the DMS Endpoint by specifying pluginName=test_decoding in Extra Connection Attributes
2. Create a new DMS task using this endpoint (using the old task may cause it to fail due to dissynchronization between the task and the logs)

It sure did resolve the issue, but we still don't know what the problem really was with the plugin that is strongly suggested everywhere in the DMS documentation (at the moment).

If you look at the diff of the version you've used before vs. the version you're using now (https://github.com/seuros/capistrano-puma/compare/v3.1.1...v5.0.2), you can see that the puma:start command (together with others) was apparently removed from the main puma.rake and instead moved to the the pluggable adapters for daemonization and systemd respectively. Judging by the readme (https://github.com/seuros/capistrano-puma#usage), Puma 5+ only allows systemd (see https://github.com/puma/puma/pull/2170), so you'll have to add install_plugin Capistrano::Puma::Systemd to your Capistrano setup (and of course make sure that your setup runs systemd properly).

If you can't/don't want to use systemd and want to stick with Puma's classic daemonization, you'll have to go with Puma 4 (gem 'puma', '< 5' in your Gemfile) until you're ready to upgrade.

The issue was one of my containers was "pending" since it depended on another container with an incorrect healthCheck command. The command always failed, causing an unhealthy state on that container, so the pending container never actually started.

error is due to

You're passing it incorrectly

You need to import models, or conforming to your other field definitions, prefix it with models. like so: