Reputation: 48486
I have a config
file in my projects's .ebextensions
directory containing
option_settings:
"aws:elasticbeanstalk:container:python:staticfiles":
"/static/": "sitetest/static/"
but my EB environment does not change the setting for /static/
in response to this being pushed to AWS.
I can verify that other config
settings in the same directory — e.g. for environment variables using
option_settings:
"aws:elasticbeanstalk:application:environment":
SOME_VAR: "foo"
or for container commands using
container_commands:
00_syncdb:
command: "python manage.py db upgrade"
leader_only: true
behave as expected.
Why isn't AWS Elastic Beanstalk's static path changing when to correspond to the setting in my config file?
Upvotes: 1
Views: 1946
Reputation: 15755
The ebextensions
are a lower precedence setting. What this means is that if you ever set anything in your ebextensions using the cli/console/api, the ebextension will no longer take effect.
You can remove the setting using the cli/api in order to get the ebextension to work again.
Using the EB CLI you can use eb config
then remove the related line from the file.
Using the AWS CLI you can use:
aws elasticbeanstalk update-environment --environment-name MyEnvName --region us-west-2 --options-to-remove Namespace=aws:elasticbeanstalk:container:python:staticfiles,OptionName=/static/
Upvotes: 3