-
Notifications
You must be signed in to change notification settings - Fork 35
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
fix: Composer prevails over env for Nginx and Composer too #409
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a couple of suggestions, but already approving the PR
# No Composer | ||
} | ||
|
||
test::helpers::composer_deploy() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion(non-blocking): with both composer_deploy
and classic_deploy
sharing most of the code base, we could create a common function named test::helpers::deploy_common
that is called by these functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, applied in 4217951
Co-authored-by: Étienne M. <EtienneM@users.noreply.github.com>
…ldpack into tests/composer_prevails
Add tests to check that:
scalingo-20
andscalingo-22
).NGINX_VERSION
composer.json
composer.json
will always prevail overNGINX_VERSION
if both are set.NGINX_VERSION
composer.json
composer.json
will always prevail overNGINX_VERSION
if both are set.I had to make quite a few changes to be able to do that in a way that follows the testing logic we have.