forked from cloudfoundry/stratos
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge 3.2.1 #383
Merged
Merged
Merge 3.2.1 #383
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
Backup/Restore endpoints & tokens
- When apps collection is fetched and exceeds maxed allowed certain monitor observables were still firing with the partial collection of apps - This led to app based stats (like count and memory) to be shown on the space cards & summary - This was caused by a correction to the pagination monitor to use 'local' monitor observables instead of non-local - The now correct observable to use did not have a filter for maxed results, so emited the bad data
CF Push: Ensure we refresh token
Fix uaa docs. Make UAA endpoint config simpler
Add docs for max list feature
…stats Ensure we filter out maxed results for local lists
…nt. (cloudfoundry#4252) * Add nodeSelector template and tests Add nodeSelector template to the helm deployment: - deployment.yaml - database.yaml - config-init.yaml Add tests to validate nodeSelector template to - deployment_test.yaml Create tests to validate nodeSelector template to - database_test.yaml - config_init_test.yaml * Add c&p fix and another nodeSelector test Add fix for c&p bug to - database.yaml - deployment.yaml Add test to validate nodeSelector template to - config_init_test.yaml Add test config to - database-test.yaml - deployment-test.yaml * Remove test Remove test to validate nodeSelector template to - config_init_test.yaml
Helm Chart: Fix Helm 3 compatibility with Release.Time
* Helm Chart: Fix Helm 3 compatibility with Release.Time * Add helm 3 lint
Version bump and change log for 3.2.0
- remove calls to fetchUserProfile - ensure entity service is used instead of monitor (will fetch profile) - update FetchUserProfileAction action to a EntityRequestAction - there's no response to update profile, so ensure we fetch profile again afterwards - also fixed issue where metrics endpoint reporting a k8s endpoint would cause a console.error
…ment Fix icon alignment on service marketplace view
…s-fix Only show metrics details on endpoint card/list when connected
…expiry CF Push: A better fix for the token expiry issue
Signed-off-by: Ben Berry <[email protected]>
Signed-off-by: Ben Berry <[email protected]>
Check sso whitelist in more places
…-notes 3.2.1 Version bump and release notes
Codecov Report
@@ Coverage Diff @@
## master #383 +/- ##
=======================================
Coverage 59.35% 59.35%
=======================================
Files 1049 1049
Lines 33499 33499
Branches 4604 4604
=======================================
Hits 19883 19883
Misses 13616 13616 |
richard-cox
commented
Jun 3, 2020
richard-cox
commented
Jun 3, 2020
src/frontend/packages/core/src/features/metrics/metrics.helpers.ts
Outdated
Show resolved
Hide resolved
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.
No description provided.