todobackend | Todobackend Web Service Application

This is probably an interraction between your (very !!!) old ansible version and the mix of old k=v + younger yaml syntax in your task. I cannot reproduce this on ansible 2.9.7.

The following syntax should probably fix your issue:

I had the same issue after upgrading to osx Mojave, and on python 3.7.2. This is what worked for me:

The password for the master user. The password can include any printable ASCII character except "/", """, or "@".

From AWS document

If you want to limit user enter unexpected character, you can use AllowedPattern

Refer to https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html#aws-specific-parameter-types

The entire Outputs: block is indented a level too far. Outputs: should not be underneath Resources: indentation-wise

Outputs documentation

I can't reproduce this problem. I put your last ifeq statement into a makefile and it works fine for me with GNU make 4.1 and 4.2.1. There must be something more unusual about your situation.

The classic way to debug issues with eval is to duplicate the line and replace the eval with info; this way make will print out exactly what it sees. Often this will show you what is wrong.

There are other confusing things about this makefile.

First, why are you using eval here in the first place? Why not just write the rule directly? There's nothing wrong with:

Can think of few possible approaches.

1. Store the secret in environment variable reference the environment variable in your compose file like this

For container launched by app service

Does ENTRYPOINT ["entrypoint.sh"] get executed before ENTRYPOINT ["echo"]?

No, ENTRYPOINT ["echo"] overrides ENTRYPOINT ["entrypoint.sh"] of the base image.

So ENTRYPOINT ["echo"] will run and it will receive:

command: - uwsgi - "--socket /var/www/someapp/someapp.sock" - "--chmod-socket=666" - "--module someapp.wsgi" - "--master" - "--die-on-term"

as argument

Assume there is no entry point in current image, does current image execute base image entry point and then command instruction launch uwsgi process with pid 1?

Yes entrypoint.sh will run. It will receive command value as argument.

entrypoint code exec $@ means: execute all the script (enterypoint.sh) arguments (uwsgi...).

exec by definition doesn't generate new process, rather loads uwsgi into memory of existing process. Because exec process is launched with pid 1, uwsgi will receive pid 1.

As shown in the TEST_RUNNER setting, the Python package is django_nose; that's what you need to use in INSTALLED_APPS rather than django-nose. (Package names must be valid Python identifiers, so they can't contain -.)

You can have multiple changeset functions.