Chore: update main #6
Merged
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
#76327) * Manage service account secrets * Wip * WIP * WIP * Revert to keep a light interface * Implement SaveExternalService * Remove unecessary functions from the interface * Remove unused field * Better log * Leave ext svc credentials out of the extsvcauth package for now * Remove todo * Add tests to SaveExternalService * Test that secret has been removed from store * Lint * Nit. * Rename commands and structs Co-authored-by: Kalle Persson <[email protected]> * Account for PR feedback Co-authored-by: Andres Martinez Gotor <[email protected]> * Linting * Add nosec comment G101 - this is not a hardcoded secret * Lowercase kvStoreType --------- Co-authored-by: Kalle Persson <[email protected]> Co-authored-by: Andres Martinez Gotor <[email protected]>
There is a sentence in the [Built-in query](https://grafana.com/docs/grafana/latest/dashboards/build-dashboards/annotate-visualizations/#built-in-query) section of the page that could use a "the" (emphasis added by me 😄) : > When you copy a dashboard using the Save As feature it will get a new dashboard id, **so annotations created on source dashboard** will no longer be visible on the copy. You can still show them if you add a new Annotation Query and filter by tags. However, this only works if the annotations on the source dashboard had tags to filter by. This PR adds "the" so the phrase reads "so annotations created on the source dashboard"
fix config bug for selecting sigv4
…ization (#76145) * add feature toggle for smart cache serialization * re-add toggle after merge conflict * switch feature toggle stage to experimental * incorporate PR feedback
…bel, label filters and no metric (#76472) allow for label values query type with label, label filters and no metric
* Add RBAC note to library panels * Update docs/sources/dashboards/build-dashboards/manage-library-panels/index.md Co-authored-by: Isabel <[email protected]> --------- Co-authored-by: Isabel <[email protected]>
…omponent (#76165) * chore: remove legacy components and classes * Update public/app/plugins/datasource/opentsdb/components/OpenTsdbDetails.tsx Co-authored-by: Tobias Skarhed <[email protected]> * chore: format and add width * chore: fix formatting * Update public/app/plugins/datasource/opentsdb/components/OpenTsdbDetails.tsx Co-authored-by: ismail simsek <[email protected]> --------- Co-authored-by: Tobias Skarhed <[email protected]> Co-authored-by: ismail simsek <[email protected]>
Remove legacy form from InfluxConfigEditor With this commit, legacy form components are remvoed from influxdb config eidtor page. Form is now using FieldSet instead.
Fix wrong language display
Co-authored-by: Todd Treece <[email protected]>
Remove redundant code and update types
* add compat layer to convert from Export model to "new" API models
…74504) * Fix migration of custom dashboard permissions Dashboard alert permissions were determined by both its dashboard and folder scoped permissions, while UA alert rules only have folder scoped permissions. This means, when migrating an alert, we'll need to decide if the parent folder is a correct location for the newly created alert rule so that users, teams, and org roles have the same access to it as they did in legacy. To do this, we translate both the folder and dashboard resource permissions to two sets of SetResourcePermissionCommands. Each of these encapsulates a mapping of all: OrgRoles -> Viewer/Editor/Admin Teams -> Viewer/Editor/Admin Users -> Viewer/Editor/Admin When the dashboard permissions (including those inherited from the parent folder) differ from the parent folder permissions alone, we need to create a new folder to represent the access-level of the legacy dashboard. Compromises: When determining the SetResourcePermissionCommands we only take into account managed and basic roles. Fixed and custom roles introduce significant complexity and synchronicity hurdles. Instead, we log a warning they had the potential to override the newly created folder permissions. Also, we don't attempt to reconcile datasource permissions that were not necessary in legacy alerting. Users without access to the necessary datasources to edit an alert rule will need to obtain said access separate from the migration.
…76439) Prevent cleanup of non-empty folders on revert
…Convert field type transformations (#76316) * Better TZ support. * Clean things up * Update convertFieldType * Update tooltips * Remove unecessary code * Prettier * Add internal TZs * Prettier * Fix tests * Make sure tests expect time with timezone * Use true lol * Centralize logic for options
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* add library panels rbac * Update docs/sources/whatsnew/whats-new-next/index.md Co-authored-by: Isabel <[email protected]> * Update docs/sources/whatsnew/whats-new-next/index.md Co-authored-by: Isabel <[email protected]> * Added date * Fixed version syntax * run prettier --------- Co-authored-by: Isabel <[email protected]>
…#76630) * Check for process and span id * Remove log * Update tests * Check for key
* update docs for whatsnew for no basic role * Update docs/sources/whatsnew/whats-new-next/index.md Co-authored-by: Isabel <[email protected]> * linting * added feature release date --------- Co-authored-by: Isabel <[email protected]>
* Implement RGM pipeline parity between editions * Use grafana/grafana-build:dev-11c8a20 * Use grafana/grafana-build:dev-261c863 * Use grafana/grafana-build:dev-2db3b18 * Switch nightly trigger for testing purposes * Use grafana-dev api key for testing * Use grafana/grafana-build:dev-d4d2e26 * Use grafana-dev api key * Use production variables * Revert nightly trigger to cron
…efactor (#76620) Cloudwatch: revert feature toggle
* Update cue to have an AuthProvider entry * Cable the new auth provider * Add feature flag check to the accesscontrol service * Fix test * Change the structure of externalServiceRegistration (#76673)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Lezer-logql: upgrade to 0.2.1 * Deps: upgrade lezer-logql
Co-authored-by: Kristin Laemmert <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* feat: add cost management to admin and put adaptive metrics and log volume under it * test: fix applinks test * chore: fix lint error * remove "new" from feature toggle description --------- Co-authored-by: Ashley Harrison <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…ing experience (#75916) * initial changes * fix indent * fix some bugs, and update fit and finish * remove inputs * change ms.portal to portal * add new dashboards, fix some links and queries * fix more links * update the default time ranges * prettier fix dashboards * update log query variables with search '*' * default the variable value to All * missed a few spots to assume that the values of the variable are in an array * fix queries for min and max duraation as well * keep variables naming consistent * fix missing parenthesis in dependencies operation query * fix some links, change todouble instead of tollong
…76717) update performance description, fix variable in perf dependency
"Release: Updated versions in package to 10.3.0" Co-authored-by: grafana-delivery-bot[bot] <132647405+grafana-delivery-bot[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…ted (#76706) * delete team related entries for an org after the org gets deleted * fix tests * one more test fix
) Fixes #76140 Co-authored-by: Giuseppe Guerra <[email protected]>
"Release: Updated versions in package to 10.3.0-pre" Co-authored-by: grafana-delivery-bot[bot] <132647405+grafana-delivery-bot[bot]@users.noreply.github.com>
* Move rotate logic into its own function * Move oauth token sync to session client * Add user to the local cache if refresh tokens are not enabled for the provider so we can skip the check in other requests
Update doc links
* Add Alerting menu in getPanelMenu * Add translations * Allow alert tab, heart icon in all panel types, and not show warning in DashobardPicker panels * Fix tests * Move alerting submenu under 'More...' item * Move create alert menu item to More... without submenu * Update translations * Revert "Allow alert tab, heart icon in all panel types, and not show warning in DashobardPicker panels" This reverts commit 225da3f. * Revert allowing alert tab and health icon for all panel types * use onCreateAlert method name in onClick instead of new function Co-authored-by: Torkel Ödegaard <[email protected]> * Move getAlertingMenuAvailability method to a /features/alerting folder and rename it to getCreateAlertInMenuAvailability * Use onCreate direclty instead of a new method * Make getCreateAlertInMenuAvailability to return a boolean --------- Co-authored-by: Torkel Ödegaard <[email protected]>
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.
What is this feature?
[Add a brief description of what the feature or update does.]
Why do we need this feature?
[Add a description of the problem the feature is trying to solve.]
Who is this feature for?
[Add information on what kind of user the feature is for.]
Which issue(s) does this PR fix?:
Fixes #
Special notes for your reviewer:
Please check that: