Add production image support

[potiuk]

---

Issue link: WILL BE INSERTED BY boring-cyborg

Make sure to mark the boxes below before creating PR: [x]

• Description above provides context of the change
• Unit tests coverage for changes (not needed for documentation changes)
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions.
• I will engage committers as explained in Contribution Workflow Example.

---

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

[mik-laj]

There is some error in the scripts.
When I ran following command:

bash breeze restart -a 1.10.6 && bash breeze -a 1.10.6

I got following error:

Installs version of Airflow: 1.10.6

Restarts the environment. Includes emptying the databases.

Fixing group permissions
Fixed group permissions

Docker image build is forced for CI image

Checking if the remote image needs to be pulled

/Users/kamilbregula/devel/google-airflow/airflow/scripts/ci/_utils.sh: line 628: AIRFLOW_REMOTE_MANIFEST_IMAGE: unbound variable

[potiuk]

/Users/kamilbregula/devel/google-airflow/airflow/scripts/ci/_utils.sh: line 628: AIRFLOW_REMOTE_MANIFEST_IMAGE: unbound variable

will take a look thanks!

[potiuk]

All corrected - please take another look

[potiuk]

Hey @ashb @kaxil - I want to merge it to 1.10.10 before we release, Is there anything else you want to comment on?

[ashb]

Taking another look now

[kaxil]

Let's do other minor changes in follow up PRs

[potiuk]

🎉 🎉 !

[dimberman]

@potiuk I can't tell if I need to reload something but I'm not seeing build-image in auto-complete

(airflow) dimberman airflow ((HEAD detached at polidea/add-production-docker-image)) (⎈ |N/A|N/A)
$ ./breeze build-
build-docs  build-only
(airflow) dimberman airflow ((HEAD detached at polidea/add-production-docker-image)) (⎈ |N/A|N/A)
$ ./breeze build-image --production-image

[feluelle]

@dimberman run breeze-complete script again. (. ./breeze-complete did it for me)

[dimberman]

@feluelle works! had to run ./breeze setup-autocomplete and then restart shell. Might be worth mentioning in the docs or UPDATING.md?

[feluelle]

Suggested change

	docker build . -f Dockerfile.ci --build-arg PYTHON_BASE_IMAGE="python:3.7-slim-buster" \
	docker build . -f Dockerfile.ci --build-arg PYTHON_BASE_IMAGE="python:3.6-slim-buster" \

[potiuk]

Solved/.

[feluelle]

There is sth. wrong.

Suggested change

	docker build . --build-arg PYTHON_BASE_IMAGE="python:3.7-slim-buster" \
	--build-arg PYTHON_MAJOR_MINOR_VERSION=3.7 --build-arg COPY_SOURCE=. \
	--build-arg COPY_TARGET=/opt/airflow --build-arg AIRFLOW_SOURCES=/opt/airflow \
	--build-arg CONSTRAINT_REQUIREMENTS=requirements/requirements-python3.7.txt" \
	--build-arg ENTRYPOINT_FILE=entrypoint.sh \
	--build-arg AIRFLOW_INSTALL_SOURCES="apache-airflow" \
	--build-arg AIRFLOW_INSTALL_VERSION="==1.10.10" \
	--build-arg CONSTRAINT_REQUIREMENTS="https://raw.githubusercontent.com/apache/airflow/1.10.10/requirements/requirements-python3.7.txt"
	--build-arg ENTRYPOINT_FILE="https://raw.githubusercontent.com/apache/airflow/1.10.10/entrypoint.sh" \
	--build-arg SOURCES_FROM="Dockerfile" \
	--build-arg SOURCES_TO="/Dockerfile" \
	--build-arg WWW_FOLDER="www_rbac"
	docker build .
	--build-arg PYTHON_BASE_IMAGE="python:3.7-slim-buster" \
	--build-arg PYTHON_MAJOR_MINOR_VERSION=3.7 \
	--build-arg AIRFLOW_INSTALL_SOURCES="apache-airflow" \
	--build-arg AIRFLOW_INSTALL_VERSION="==1.10.10" \
	--build-arg CONSTRAINT_REQUIREMENTS=requirements/requirements-python3.7.txt" \
	--build-arg ENTRYPOINT_FILE=entrypoint.sh \
	--build-arg AIRFLOW_SOURCES_FROM="Dockerfile" \
	--build-arg AIRFLOW_SOURCES_TO="/Dockerfile" \
	--build-arg WWW_FOLDER="www_rbac"

Like this @potiuk ?

[potiuk]

@feluelle works! had to run ./breeze setup-autocomplete and then restart shell. Might be worth mentioning in the docs or UPDATING.md?

I think it really depend on your setup. simply '. ./breeze-complete' should do. Did you have another directory with airflow somewhere? Tejh setup-autocomplete sets up a symbolic link to breeze-complete and only one can be active at the same time ... It's a bit tricky to get it right if you have more than one breeze command... The command itself will work though (it will use correct definition). I keep the master v1_10_test in sync so most of the auto-complete is good for both (some values like python version are not) and eventually you will get it right next time you get into the shell...

Not sure if UPDATING.md is for those dev tools though.