Error generating test firewall data from container-down state

[matt852]

Environment

• Python version: 3.11
• Nautobot version: 1.5.7
• nautobot-plugin-firewall-model version: 1.2.0a0

Expected Behavior

The test data should generate properly, and the command should execute successfully. Even with the container in a stopped state, I expect the necessary container(s) to be brought up and the test data populated.

Observed Behavior

I get the following error in my terminal:

(nautobot-firewall-models-py3.11) ➜  nautobot-plugin-firewall-models git:(main) ✗ invoke testdata
Running docker-compose command "ps --services --filter status=running"
Running docker-compose command "run --entrypoint 'nautobot-server create_test_firewall_data' nautobot"
[+] Running 2/0
 ⠿ Container nautobot_firewall_models-db-1     Created                                                                                                              0.0s
 ⠿ Container nautobot_firewall_models-redis-1  Created                                                                                                              0.0s
[+] Running 2/2
 ⠿ Container nautobot_firewall_models-redis-1  Started                                                                                                              0.4s
 ⠿ Container nautobot_firewall_models-db-1     Started                                                                                                              0.4s
usage: nautobot-server create_test_firewall_data [-h] [--version] [-v {0,1,2,3}] [--settings SETTINGS] [--pythonpath PYTHONPATH] [--traceback] [--no-color]
                                                 [--force-color] [--skip-checks]
nautobot-server create_test_firewall_data: error: unrecognized arguments: nautobot-server runserver 0.0.0.0:8080

Steps to Reproduce

1. Clone this Git repo and build the containers normally using invoke build
2. Before running the instance, run the command invoke testdata
3. The previously mentioned error occurs
4. Start the container using invoke start
5. Run the invoke testdata command again. This time it should succeed.