Currently there are multiple deploy_stack.sh files and the user has to select the version appropriate to the target architecture so that the correct images are deployed. Further, the armhf deploy script lacks the basic auth by default scripting that is in the x86_64 version.
This change adds a case/select to deploy_stack.sh that will determine the hardware architecture and select the appropriate docker-compose file.
The deploy_stack.armhf.sh is also changed, rather than deleted, so that existing references are still valid.
Signed-off-by: Richard Gee <richard@technologee.co.uk>
This change set downloads the CDN resources for the gateway
and bundles them with the other static resources for the UI.
This is needed for situations where a user does not have access
to the CDN either because of firewall rules or network policy.
The files and versions remain the same, only now loaded locally
with directory paths matching the CDN paths.
Signed-off-by: Burton Rheutan <rheutan7@gmail.com>
A talk on IstaCon, Sofia, workshop on OpenFest, Sofia, and a
lightning talk during the same event are added to the events list
Signed-off-by: Ivana Yovcheva (VMware) <iyovcheva@vmware.com>
Issue #955 suggested that the watchdog binaries should have associated sha256 files to help assure the veracity of the built artefacts. This change mirrors the method employed on
faas-cli to generate and deploy the sha256 hash for each flavour of the current watchdog.
Signed-off-by: Richard Gee <richard@technologee.co.uk>
Incubator link is pointing to the main OpenFaaS GitHub organization instead of the OpenFaaS-Incubator organization.
Signed-off-by: Shaun Berryman <shaun@shaunberryman.com>
- this reinstates the cache to reduce the count of lookups to the
provider when checking if scaling is needed.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- this change is needed for Docker Swarm which may give an error
when several concurrent requests come in to scale a deployment.
Tested on Docker Swarm before/after with the hey tool and figlet
scaled down to zero replicas.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- PR #929 introduced the ability to generate passwords for the
gateway admin user, this is a good step forwards for Windows
users. It did introduce an inconsistency in the format that
passwords are stored by not using a form of hashing. Hashing
of secrets is used extensively within OpenFaaS/OpenFaaS Cloud
whether with Swarm or Kubernetes via helm. If there are
concerns about using a hashed value for a password I would
suggest raising an issue to track this and have any decision
we make applied for all users (not just PowerShell users).
As a compromise I've introduced hashing by default and added
a new flag called -noHash which can be used to replicate the
behaviour of the original PR.
After feedback from other contributors I also looked into whether
the flag syntax could match the existing syntax but left this as
is. Bash will use --no-auth and PowerShell will use --noAuth.
This was tested on Docker Swarm on Windows.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
