Release/0.8.4 #38
Merged
Release/0.8.4 #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
iakkus
commented
Jun 15, 2020
•
iakkus
commented
- New features for updating user profiles (issue Name and password change operations #6) and deleting user accounts (issue Deleting user accounts #5)
- Cleanup unused management service functions (issue cleanup unused functions from management service #24)
- Remove CORS requests from GUI (issue browser CORS checks for GUI actions #23)
- Bug fix Makefile for GUI (issue Error in building docker image for GUI #29)
- Additional build tools for thrift; upgrade thrift version to 0.13
- Stability improvements for Riak nodes in Kubernetes
- Various other stability improvements
…or a logged in user; deleting a user account deletes all tokens; modification to SDK for corresponding action; modification to test utils for cleanup test
…-specific flags, so they are going to be handled from branch 'feature/asl_knix_flag'. fixes #20
…tings.env; disallow 'space' character in user emails when signing up in management service
In K8s deployment, riak pods of a statefulset can get new different IP addresses when restarting. Previously, PVC wouldn't make sense, now a failing pod can be recovered with attached PVC and still be able to return to the cluster. Still more testing needed to confirm scaling and recovery doesn't cause scripts (e.g. cluster join) to fail the restart of a pod
…it still a placeholder to be handled by issue #25
…xecution window also shouldn't require any CORS requests.
…ement Feature/cleanup management
…ent service via nginx are now derived from the Release name of the helm charts. Furthermore: 1) The host header should include the knative domain name configured in the config-domain configmap of knative. So the Host header should be: wf-<ReleaseName>-management.<knativeDomain>. knativeDomain variable has been added to values.yaml. 2) The url used to connect should be http://wf-<ReleaseName>-management (which also the name of the route configured by knative for the management service)
…le for future additional parameters (build_env.mk)
…snt have any effect there
…or_management Feature/remove cors for management; fixes #23
…n json (like put encodes the passed value as JSON)
…onfig template to deploy/ansible/
…ntend Makefile dependencies for thrift file generation
values.yaml cannot use scripting, so helper nginx.mgmtService is used to default to wf-{ release }-management.{ namespace }.example.com
…ations Feature/password operations
…(to be added back from feature/asl_knix_flags branch)
Feature/delete account
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.