[FEAT] Single-Command Containerization for Pre-Built FastAPI Applications

[Coopyrightdmin]

Problem Statement

When a Python code is already built on FastAPI, we want to ensure that only the containerization process is done without duplicating efforts or introducing potential errors by modifying the FastAPI setup.

Benefits

1. Reduces the risk of errors that could arise from unnecessary modifications to a pre-existing FastAPI setup.
2. Speeds up the deployment process since the focus is only on containerization.
3. Simplifies the workflow for developers, allowing them to leverage their existing FastAPI codebase without redundant steps.

Additional context

FastAPI is a modern, fast (high-performance) web framework for building APIs with Python. Given its increasing popularity and adoption rate, it's crucial to provide a seamless containerization process for projects that already use it.

Priority/Severity

• [x] High (This will bring a huge increase in performance/productivity/usability/legislative cover)
• [ ] Medium (This will bring a good increase in performance/productivity/usability)
• [ ] Low (anything else e.g., trivial, minor improvements)

[Coopyrightdmin]

To address the concern of unnecessary modifications or duplications when containerizing pre-existing FastAPI setups, we've made the following updates:

• Introduced the --skip-fastapi option: This allows users to bypass the FastAPI generation process, ensuring that existing FastAPI setups are not inadvertently altered.
• Enhanced error handling: The code generation process now checks for any import fastapi statements. If identified, the process will halt, preventing any unintentional modifications to the original FastAPI setup.
• Source script renaming: By default, the source script will be renamed to <basename>-api.py. This ensures clarity and avoids potential naming conflicts during the containerization process.