Convert all sample-functions to use curl to get the watchdog as
it can be cached by Docker. Issue #841
Signed-off-by: Radoslav Dimitrov <rdimitrow@gmail.com>
Convert all sample-functions to use curl to get the watchdog as
it can be cached by Docker. Issue #841
Signed-off-by: Radoslav Dimitrov <rdimitrow@gmail.com>
Convert all sample-functions to use curl to get the watchdog as
it can be cached by Docker. Issue #841
Signed-off-by: Radoslav Dimitrov <rdimitrow@gmail.com>
Idea from Matthew Holt, using the haveibeenpwned API to query
whether a password has been found in a data-breach.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
1. Add new annotation attributes which may be used
by the back-end for making scheduling or routing decisions.
2. Updated tests/README.md to give clearer instructions on creating and
tearing down the stack required to run the integration tests
3. Update ci.sh
* Fail as soon as an error is encountered
* Allow script to run locally in development environment, test if repos
are already cloned etc..
* Deploy ./stack.yml used by existing integration tests
Signed-off-by: Edward Wilde <ewilde@gmail.com>
**What**
- Update the documentation about secret management to note the changed
file location
- Remove the documentation on secret rotation, because this will not
currently work
- Update apikey-secret and ApiKeyProtected-Secrets to read secret values
from both the old and the new locations
**Why**
- Recent updates to faas-swarm and faas-netes changed the mount location
of secrets. These changes update the docs to reflect this change.
Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>
Issue #660 has been open for a while to update to 1.9.6, this
performs the update to the latest in the 1.9 release (1.9.7)
Signed-off-by: Sean Smith <sean@wwsean08.com>
Following the existing README instructions would result in an error
when the user attempted to create the secret. This small change
remediates the instruction so that the secret is successfully created.
Signed-off-by: rgee0 <richard@technologee.co.uk>
This updates fwatchdog to latest version (0.7.9) in all templates
in sample-functions and faas version in the documentation
Signed-off-by: Ivana Yovcheva (VMware) <iyovcheva@vmware.com>
Update the NodeInfo sample function to use latest
watchdog version (0.7.7) to support both GET and POST method.
Signed-off-by: Vivek Singh <vivekkmr45@yahoo.in>
This commit bumps the non-arm gateway from 0.7.0 to 0.7.1 and the arm
variants from 0.6.9 to 0.7.0.
It also updates all watchdog versions to the 0.7.1 release.
Signed-off-by: John McCabe <john@johnmccabe.net>
**What**
- Move the new secrets sample function to ApiKeyProtected-Secrets
- Bring back the original ApiKeyProtected sample function
Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>
**What**
- Add a description for the secret key to the api swagger spec.
- Remove optional examples from the secret management guide.
- Update the ApiKeyProtected README to point at the new guide.
- Refactor the `makeSpec` function to accept the already assembled secrets
array because this should be easier to unit test.
Signed-off-by: Lucas Roesler <lucas.roesler@gmail.com>
**What**
- During function creation, accept an array of strings defining swarm secrets
that are required for the service
- Update docs
- Add new guide on using the secrets capability
- Add new sample function to highlight using environment variables
- Update `ApiKeyProtected` sample function to utilize the new secrets
capabilities
**Why**
- This allows secrets to remain encrypted at rest instead of being unencrypted
in environment variables and yaml files.
Fixes#285
Signed-off-by: Lucas Roesler <lucas.roesler@gmail.com>
