Fix #3236: Add support for secure docker compose with an env file

[vivekratnavel]

Describe your changes :

See #3236

To bring up a secure docker compose cluster, one can set up an env file like this and pass the env file path in command line:

AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
AUTHORIZER_REQUEST_FILTER=org.openmetadata.catalog.security.JwtFilter
AUTHORIZER_ADMIN_PRINCIPALS=admin
AUTHORIZER_INGESTION_PRINCIPAL=ingestion-bot
AUTHORIZER_PRINCIPAL_DOMAIN=open-metadata.org
AUTHENTICATION_PROVIDER=google
AUTHENTICATION_PUBLIC_KEY=https://www.googleapis.com/oauth2/v3/certs
AUTHENTICATION_AUTHORITY=https://accounts.google.com
AUTHENTICATION_CLIENT_ID=709849217090-n7s8oc4cvpffubraoi5vbr1s0qfboqvv.apps.googleusercontent.com
AUTHENTICATION_CALLBACK_URL=http://localhost:8585/callback

metadata docker -env-file ~/env_open_metadata -f ~/docker-compose --start

Type of change :

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• I have performed a self-review of my own.
• I have tagged my reviewers below.
• I have commented on my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• All new and existing tests passed.

Reviewers

[github-actions]

The Python checkstyle failed.

Please run make py_format in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[harshach]

@vivekratnavel can you run the python checkstyle

[harshach]

Fix python checkstyle

[vivekratnavel]

@harshach @akash-jain-10 Thanks for the review. One thing to note with this patch is that when security is enabled, the initial ingestion will fail because it will not have the secret to access the secure APIs. But, if the user tries to ingest with sample-data.json with the secret key config, it will succeed.

[sonarcloud]

[open-metadata-ingestion] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication

[vivekratnavel]

I have created #3259 to add a flag to skip ingestion during startup. That should improve the user experience