Add warnings around current versions EOL date

[sunank200]

Add a warning to the Airflow UI for the following scenarios:

• When the current version will reach its end of life (EOL) in 30 days(by default but this is configurable with an environment variable) or less.
• When the current version has already reached its end-of-life.

This pull request provides options to dismiss the end-of-life (EOL) warnings for a configurable number of days (by default, it's set to 7 days). It also provides an option to completely disable the EOL warning with an environment variable.

Configuration

The following environment variables can be set to configure the behaviour of the Astronomer update checks and EOL warnings:

• AIRFLOW__ASTRONOMER__EOL_WARNING_OPT_OUT: Sets whether to opt out of EOL warnings. The default is "False".
• AIRFLOW__ASTRONOMER__EOL_DISMISSAL_PERIOD_DAYS: Sets the period for dismissing EOL warnings. The default is 7 days.
• AIRFLOW__ASTRONOMER__EOL_WARNING_THRESHOLD_DAYS: Sets the threshold for showing EOL warnings. The default is 30 days.

Example Usage

To set these environment variables, you can add the following lines to your environment configuration:

export AIRFLOW__ASTRONOMER__EOL_WARNING_OPT_OUT="False"
export AIRFLOW__ASTRONOMER__EOL_DISMISSAL_PERIOD_DAYS=7
export AIRFLOW__ASTRONOMER__EOL_WARNING_THRESHOLD_DAYS=30

Additionally, as part of this pull request, I have included a migration step for the database in plugins.py.

I tested the airflow deployment by manually adjusting the EOL in the database:

closes: #63

[jedcunningham]

Hmm, I wonder if we need to be more defensive. What happens if we go from this version with EOL stuff to a version without it? Probably fine? But we need to test that since we can't block that downgrade.

[cmarteepants]

Hmm, I wonder if we need to be more defensive. What happens if we go from this version with EOL stuff to a version without it? Probably fine? But we need to test that since we can't block that downgrade.

Yes rollbacks makes that a possibility.

[vatsrahul1001]

@sunank200 I am getting the below error when I am trying this on Astro cloud

[sunank200]

@sunank200 I am getting the below error when I am trying this on Astro cloud

@vatsrahul1001 can you try once with new wheel file as I had changed code last night. Did you try it on local? It works for me locally. I will try on astro cloud today.

[vatsrahul1001]

@sunank200 same behaviour with new wheel file. This is the deployment link

[sunank200]

Use alter command of SQLalchemy for adding columns

@vatsrahul1001 can you test now? It should be fixed. I am able to run on Astro cloud here