Adding check to ensure the s2i assemble user is allowed if the --allowed-uids flag is set.
The assemble user can come from one of two sources:
1. --assemble-user flag
2. builder image io.openshift.s2i.assemble-user label
The assemble user overrides the default image user for an s2i build.
However, if the base image has ONBUILD instructions with USER directives,
all USER directives will be checked to ensure compliance.
Bug 1582976
This fixes an error when the git repo is empty, e.g. the user only ran
`git init`. If the repo is empty, we use system copy commands instead
of git commands, and warn the user.
Also added errors for if there is a .git directory in the project, but
a Git binary is not installed. Changed various function headers to throw
these errors.
From now you can create final image that is based on the image that is
different than builder image. To use it provide --runtime-image option
with image that will be used in runtime.
Also specify --runtime-artifact option (one or more times) with a list
of files and directories that will be copied into resulting image.
Alternatively this mapping can be extracted from the
io.openshift.s2i.assemble-input-files annotation on a runtime image.
To execute custom logic to arrange image to a desired state, you can
leverage "assemble-runtime" script. You can 1) put it .s2i/bin directory
with application sources 2) download it from remote location (-s option)
or 3) have it inside a runtime image (but don't forget to add
io.openshift.s2i.scripts-url label on it).
- don't use deprecated image: openshift/wildfly-8-centos -> openshift/wildfly-100-centos7
- update docs to use --pull-policy instead of deprecated --force-pull.
- replace .stifile by .s2ifile in --use-config option description.
