v4.0.1 minor improvements

Full Changelog: v4.0.0...v4.0.1

v4.0.0 - Github APP Authentication & Authorization with Device Flow

Now you can authenticate and authorize directly by installing the cctray-auth Github app and perform app-device-flow authorization to obtain a Github token, making the setup more intuitive and secure.

This eliminates the overhead of creating your own Github app as it was previously required to use the app-auth mode.

What's changed:

• You can now run the service in app-auth mode by installing the cctray-auth GitHub app and setting the GITHUB_APP_TOKEN environment variable.
• The token can be obtained by accessing the new endpoint /auth, which will initiate the device-flow authorization.
• The APP_AUTH_PRIVATE_KEY_B64 and APP_AUTH_INSTALLATION_ID environment variables have been removed and are no longer supported.

For more detailed information, please go through the README file.

v3.2.0 - General improvements

• Expect a Base64 encoded private key of Github App for consistency across environments (EKS, K8s ECS, Docker)
• Improve logs

Fixes /health route

• Bug fix for /health route

Modularize the source code

3.1.0

• Modularize the source code
• Create separate modules for app, helpers, routes & config
• Update unit tests

Fix: mode argument override using Entrypoint

• Fix for v3.0.0
• Update the Dockerfile
• Allow overriding the python command attribute to switch b/w pat-auth and app-auth
• Update readme

Introduce Github App based authentication

• Add support for Github App based authentication
• This increases the API rate limit from 5000 to 15000 if used.
• Return git commit ID as buildlabel in the XML

New endpoint for checking the health status

• /health endpoint
• Returns HTTP 200, with JSON response containing the status and version:

{"status":"ok","version":"2.2.0"}

Added Authentication functionality

The app now support Basic auth, set the following two environment variables at the run time:

BASIC_AUTH_USERNAME=<value>
BASIC_AUTH_PASSWORD=<value>

v2.0.0

Multi threading and improved performance

• Add a new method, extract and re-use
• Refactor and reduce duplicity
• Use response raise for status for raising HTTP Errors
• Add docstrings and improve code linting to 10/10
• Update unit tests as per refactoring