Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating where to pull requirements from (not pypi) #402

Open
syynni opened this issue Oct 16, 2024 · 0 comments
Open

Updating where to pull requirements from (not pypi) #402

syynni opened this issue Oct 16, 2024 · 0 comments

Comments

@syynni
Copy link

syynni commented Oct 16, 2024

Hello,
Is it possible to configure MWAA and aws-mwaa-local-runner to use a different package repo than pypi?

We need to use our own CA repository, and have tried out this example: https://docs.aws.amazon.com/mwaa/latest/userguide/samples-code-artifact.html w/ PIP_INDEX_URL and PIP_EXTRA_INDEX_URL

But modifying our startup.sh with these doesn't seem to have the expected effect -
The environment variables don't appear to be configured in the docker container that is started up (env shows several environment variables, but not PIP_EXTRA_INDEX_URL or PIP_INDEX_URL) but directly updating these env variables in the docker container itself and then running any pip commands does seem to pull from the expected CA repo.

Any information on the best approach for this would be much appreciated.

Alternatively, if anyone just knows how to get env variables properly set in the containers where Airflow will be installing the dependencies, that's mostly what I need to know!

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant