Skip to content

Commit

Permalink
Bump version to 0.7.0 for beta release (#670)
Browse files Browse the repository at this point in the history
* Fix a couple shellcheck errors
* Add timeout to k8s demo curling to prevent infinite loop
* Clarify keychain_provider README
* Update CHANGELOG / VERSION for beta release
  • Loading branch information
jonahx authored and izgeri committed Mar 26, 2019
1 parent 536b62e commit bc398be
Show file tree
Hide file tree
Showing 5 changed files with 50 additions and 12 deletions.
39 changes: 38 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,44 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

## [Unreleased]

## [0.7.0] 2019-03-26

### Added
- Added ability to verify plugin checksums

- Add ability to verify plugin checksums
- Add kubernetes secrets provider to README.md
- Note styling in Kubernetes tutorial
- Add link to /tutorials in the top nav
- Add daily build trigger
- Add redirect link capabilities
- Add version to README.md
- Add a README for the shared library
- C shared library exposing secret providers (POC)
- Add custom 404 page

### Changed

- Update Kubernetes Tutorial for Simplicity and Clarity
- Simplify fast k8s tutorial
- Update CTA links
- Refactor mysql/NativePassword to take bytes
- Clean up Go memory of secrets
- Refactor MySQL handler for readability and consistency
- Updating website build to gen godocs in go img

### Fixed

- Fix kubernetes secrets example in README
- Fix kubernetes-secrets-provider hash
- Remove target=blank from footer links
- Fix broken website publishing
- Fix all non-TODO CodeClimate issues
- Fix ssh hadler test naming
- Make ssh-handler integration test pull images before build
- Remove references to doc layout and update links
- Remove hashicorp root cert to fix broken build
- Fix the vault test that broke due to vault CLI updates
- Re-enable ssh-handler tests

## [0.6.4] 2019-02-01

Expand Down Expand Up @@ -203,3 +239,4 @@ The first tagged version.
[0.6.2]: https://github.com/cyberark/secretless-broker/compare/v0.6.1...v0.6.2
[0.6.3]: https://github.com/cyberark/secretless-broker/compare/v0.6.2...v0.6.3
[0.6.4]: https://github.com/cyberark/secretless-broker/compare/v0.6.3...v0.6.4
[0.7.0]: https://github.com/cyberark/secretless-broker/compare/v0.6.4...v0.7.0
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.6.4
0.7.0
2 changes: 1 addition & 1 deletion demos/k8s-demo/02_app_developer_steps
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ kubectl --namespace quick-start-application-ns \
printf 'Waiting for application to boot up\n'
printf '(This may take more than 1 minute)\n'

until curl --silent "${APPLICATION_URL}/pets" >/dev/null; do
until curl --connect-timeout 3 --silent "${APPLICATION_URL}/pets" >/dev/null; do
printf "."
sleep 3
done
Expand Down
4 changes: 2 additions & 2 deletions test/manual/k8s_crds/deploy
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
#!/bin/bash -e

CURRENT_DIR=$(dirname $0)
CURRENT_DIR=$(dirname "$0")

echo "Stopping deployment..."
./stop_deployment || true

echo "Deploying..."
kubectl apply -f $CURRENT_DIR/deployment.yaml
kubectl apply -f "$CURRENT_DIR/deployment.yaml"

echo "Deployment done!"
15 changes: 8 additions & 7 deletions test/manual/keychain_provider/README.md
Original file line number Diff line number Diff line change
@@ -1,17 +1,18 @@
# keychain_provider tests

Note: This directory does not contain `start`, so it will not be run by the wrapper script `./bin/test`.
The OS X Keychain Provider is meant for interactive use by a user, which
is why this test is "manual".

The reason is that (keychain_provider_test.go)[keychain_provider_test.go] will open a confirmation dialog, which does not play well with automation.

The OS X Keychain Provider is meant for interactive use by a user; this dialog is a security feature of the OS.
The (keychain_provider_test.go)[keychain_provider_test.go] will open a
confirmation dialog during this test, and you'll need to click "Allow"

To run the test locally if you are working on a Mac, just run

```
./start
./test
```

from this directory. The `start` script prepares your local
environment by adding a secret to your OSX Keyring. Note that you may be
prompted to grant access to your OSX Keyring in order for this test to run
properly. To clean up after running the test, you can run `./stop`.
environment by adding a secret to your OSX Keyring. To clean up after running
the test, you can run `./stop`.

0 comments on commit bc398be

Please sign in to comment.