Currently there needs to be a AWS profile configured to tag images on
AWS. With this change, it's also possible to use the standard[0] AWS
environment variables to provide the credentials for login.
Currently a AWS_PROFILE needs to be configured with the name of the
NAMESPACE that is used. Eg. when trying to tag images under ubuntu/,
the AWS profile "ubuntu" must be there. That is not a good name where
multiple profiles are available.
So allow setting the env var AWS_PROFILE and use the profile set
there.
tag-images.sh: do not tag stable/beta/candidate the devel release
The release under development should not be tagged with
stable/beta/candidate because it's currently under development.
So use distro-info to get the release under development and skip that
image for tagging.
Note: the distroname tag and release version tag are still added.
The ubuntu base image is now also available on dockerhub in the ubuntu
namespace[0]. So allow using the tag-images.sh script with the
dockerhub registry.
software-versions.sh: Look up the package versions in docker images
Determine the docker image names for the software packages and attempt
to download them locally. If that succeeds, create a temporary
container and run it to look up the installed version of the software.
Previously we used a binary metapackage to help determine the source
package name for a given Ubuntu release. The installed binary package
we're looking at in the image is not necessarily the same as the
metapackage, and in some cases its name is versioned like the source
package. So, for example with mysql we have 'mysql-{M.N}' as the source
package, 'mysql-server' as the metapackage used to determine M.N, and
then 'mysql-server-core-{M.N}' as the installed binary package we're
looking up.
shellcheck flagged some lines as needing quoting that actually need to
not have quoting because we are intentionally using that behavior for
dividing up the parts of a version number.
Restore the original quoting and add a shellcheck disable.