Consolidates the Dependabot minor/patch Go-dep bumps that move together
through the workspace dependency graph. The same deps repeat across many
module go.mod files, and apps/provisioning + apps/secret already pin
grafana-app-sdk@0.56.0 on main, so the whole workspace must move as one
coherent set rather than 23 trivial PRs.
Direct dependency bumps (exact Dependabot targets, all within current major):
- github.com/grafana/grafana-app-sdk 0.53.2 -> 0.56.0
(root + apps/advisor, alerting/notifications, alerting/rules,
correlations, dashboard, iam, playlist, plugins, shorturl)
- github.com/grafana/grafana-aws-sdk 1.4.3 -> 1.4.5 (root)
- github.com/beevik/etree 1.4.1 -> 1.6.0 (root)
- github.com/russellhaering/goxmldsig 1.4.0 -> 1.6.0 (root)
- github.com/opentracing-contrib/go-grpc 0.1.2 -> 0.1.3 (root)
- gocloud.dev 0.44.0 -> 0.46.0 (root)
- cloud.google.com/go/kms 1.25.0 -> 1.31.0 (root)
- buf.build/gen/go/parca-dev/parca/connectrpc/go and protocolbuffers/go
-> 1.20.0-/1.36.11-20260523035409-ca8a9e862107.1 (root)
- golang.org/x/net was already at 0.55.0 on main (no change needed).
grafana-plugin-sdk-go is carried to 0.291.1 transitively (required by
grafana-aws-sdk@1.4.5); it still exports QueryTypeDefinitionSpec.Examples
so the query schema code compiles. The explicit bump to 0.292.1 is NOT
taken here (see below).
Transitive consequences of grafana-app-sdk@0.56.0 (faithful to what
Dependabot itself produces via MVS): k8s.io/* 0.35.3 -> 0.36.x,
grafana/authlib + authlib/types advanced, go directive 1.26.1 -> 1.26.2
(app-sdk@0.56.0 declares go 1.26.2; go.work synced to match — the
member modules already required 1.26.2 on main).
Source changes required to compile against the bumped SDKs (mirrors
upstream grafana/grafana exactly, no unrelated drift):
- authlib types.AuthInfo gained GetAccessToken(); implement it on the
three identity.Requester types — StaticRequester, SignedInUser and
authn.Identity — each adding an AccessToken field + getter alongside
the existing GetIDToken.
- grafana-app-sdk resource.ClientGenerator now requires DiscoveryClient()
(and already required GetCustomRouteClient); implement both on
lazyClientGenerator and on the plugins install test fake.
Verification (Go workspace == CI build model; GOWORK on):
go build ./... PASSES for root and all nine bumped app modules and
pkg/apimachinery; go test -short PASSES for every app module,
pkg/apimachinery/identity, and the touched root packages
(services/user, services/authn, services/apiserver). Heavy root-wide
test suites were not run.
Deferred (left to their open Dependabot PRs): grafana-plugin-sdk-go
0.292.1. That release removes QueryTypeDefinitionSpec.Examples and the
QueryExample type, which requires a non-trivial upstream feature refactor
of pkg/registry/apis/query/queryschema (examples move to
data.QueryExamples) that is beyond a dependency bump.
Co-authored-by: Antje Worring <worringantje@gmail.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
* revert 1.26
* more updates
* new go.sum
* revert some go.mod entries
* updagte swagger and openapi
* more reverting and codegen
* test fix and make gen-apps
* [chore] Upgrade grafana-app-sdk to v0.51.3, set app roles to empty for each app so that manifest codegen is unchanged.
* Fix linter issues in dashboard conversion tests, ignore linter staticcheck in the IAM app to avoid any additional changes.
* Initial reconciler implementation
* Refactor how zanzana gets the k8s client to list crd's
* Add toggle to disbale RBAC reconciler
* Make auth work with iam-apiserver
* Fix authorizer for standalone iam api server
* Add rolebinding storage to the standalone iam api server
* Increase unifi store page size to 10000
* Remove duplicate time based reconciliation logic
* Implement mt-reconciler running in embedded zanzana
* Consolidate reconciliation interval configuration for zanzana reconcilers
* Revert unrelated changes
* Re-word docs
* pre-allocate tuples where possible.
* Add translators test
* Fix user name
* remove hard-coded GVR's
* Make queue size configurable
What:
Extend the aggregator configurator interface with a method that allows
injecting a CRD informer.
Why:
To enable support for registering APIs based on installed CRDs.
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
* descritpion and transformations
* add fieldMinMax to schema
* add nullValueMode to schema
* convert actions
* disabled prop in transformations
* update
* fix
* gauge
* remove index (deprecated) and decimals as strings
* gofmt
* codegen
* lint
* open api
* feat(pyroscope): Exemplar support for series queries
use enum flag, add exemplar flag to explore
disable exemplars on explore as well
tests
feature toggle
fixing tests
* resolve conflicts
* lint
* Secrets: changes to allow a 3rd party keeper / secret references
* fix test
* make gofmt
* lint
* fix tests
* assign aws secrets manager to @grafana/grafana-operator-experience-squad
* rename Keeper.Reference to Keeper.RetrieveReference
* rename ModelSecretsManager to ModelAWSSecretsManager
* validator: ensure that only one of keeper.Spec.Aws.AccessKey or keeper.Spec.Aws.AssumeRole are set
* move secrets manager dep / go mod tidy
* move secrets manager dep
* keeper validator: move 3rd party secret stores validation to their own functions
* add github.com/aws/aws-sdk-go-v2/service/secretsmanager pkg/extensions/enterprise_imports
* make update-workspace
* undo go.mod changes in /apps
* make update-workspace
* fix test
* add github.com/aws/aws-sdk-go-v2/service/secretsmanager to enterprise_imports
* make update-workspace
* gcworker: handle refs
* make update-workspace
* create toggle: FeatureStageExperimental
* allow features.IsEnabled for now
* format
* Deprecate Legacy Storage Migration in Backend
* Change the messaging around legacy storage
* Disable cards to connect
* Commit import changes
* Block repository creation if resources are in legacy storage
* Update error message
* Prettify
* chore: uncomment unified migration
* chore: adapt and fix tests
* Remove legacy storage migration from frontend
* Refactor provisioning job options by removing legacy storage and history fields
- Removed the `History` field from `MigrateJobOptions` and related references in the codebase.
- Eliminated the `LegacyStorage` field from `RepositoryViewList` and its associated comments.
- Updated tests and generated OpenAPI schema to reflect these changes.
- Simplified the `MigrationWorker` by removing dependencies on legacy storage checks.
* Refactor OpenAPI schema and tests to remove deprecated fields
- Removed the `history` field from `MigrateJobOptions` and updated the OpenAPI schema accordingly.
- Eliminated the `legacyStorage` field from `RepositoryViewList` and its associated comments in the schema.
- Updated integration tests to reflect the removal of these fields.
* Fix typescript errors
* Refactor provisioning code to remove legacy storage dependencies
- Eliminated references to `dualwrite.Service` and related legacy storage checks across multiple files.
- Updated `APIBuilder`, `RepositoryController`, and `SyncWorker` to streamline resource handling without legacy storage considerations.
- Adjusted tests to reflect the removal of legacy storage mocks and dependencies, ensuring cleaner and more maintainable code.
* Fix unit tests
* Remove more references to legacy
* Enhance provisioning wizard with migration options
- Added a checkbox for migrating existing resources in the BootstrapStep component.
- Updated the form context to track the new migration option.
- Adjusted the SynchronizeStep and useCreateSyncJob hook to incorporate the migration logic.
- Enhanced localization with new descriptions and labels for migration features.
* Remove unused variable and dualwrite reference in provisioning code
- Eliminated an unused variable declaration in `provisioning_manifest.go`.
- Removed the `nil` reference for dualwrite in `repo_operator.go`, aligning with the standalone operator's assumption of unified storage.
* Update go.mod and go.sum to include new dependencies
- Added `github.com/grafana/grafana-app-sdk` version `0.48.5` and several indirect dependencies including `github.com/getkin/kin-openapi`, `github.com/hashicorp/errwrap`, and others.
- Updated `go.sum` to reflect the new dependencies and their respective versions.
* Refactor provisioning components for improved readability
- Simplified the import statement in HomePage.tsx by removing unnecessary line breaks.
- Consolidated props in the SynchronizeStep component for cleaner code.
- Enhanced the layout of the ProvisioningWizard component by streamlining the rendering of the SynchronizeStep.
* Deprecate MigrationWorker and clean up related comments
- Removed the deprecated MigrationWorker implementation and its associated comments from the provisioning code.
- This change reflects the ongoing effort to eliminate legacy components and improve code maintainability.
* Fix linting issues
* Add explicit comment
* Update useResourceStats hook in BootstrapStep component to accept selected target
- Modified the BootstrapStep component to pass the selected target to the useResourceStats hook.
- Updated related tests to reflect the change in expected arguments for the useResourceStats hook.
* fix(provisioning): Update migrate tests to match export-then-sync behavior for all repository types
Updates test expectations for folder-type repositories to match the
implementation changes where both folder and instance repository types
now run export followed by sync. Only the namespace cleaner is skipped
for folder-type repositories.
Changes:
- Update "should run export and sync for folder-type repositories" test to include export mocks
- Update "should fail when sync job fails for folder-type repositories" test to include export mocks
- Rename test to clarify that both export and sync run for folder types
- Add proper mock expectations for SetMessage, StrictMaxErrors, Process, and ResetResults
All migrate package tests now pass.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Update provisioning wizard text and improve resource counting display
- Enhanced descriptions for migrating existing resources to clarify that unmanaged resources will also be included.
- Refactored BootstrapStepResourceCounting component to simplify the rendering logic and ensure both external storage and unmanaged resources are displayed correctly.
- Updated alert messages in SynchronizeStep to reflect accurate information regarding resource management during migration.
- Adjusted localization strings for consistency with the new descriptions.
* Update provisioning wizard alert messages for clarity and accuracy
- Revised alert points to indicate that resources can still be modified during migration, with a note on potential export issues.
- Clarified that resources will be marked as managed post-provisioning and that dashboards remain accessible throughout the process.
* Fix issue with trigger wrong type of job
* Fix export failure when folder already exists in repository
When exporting resources to a repository, if a folder already exists,
the Read() method would fail with "path component is empty" error.
This occurred because:
1. Folders are identified by trailing slash (e.g., "Legacy Folder/")
2. The Read() method passes this path directly to GetTreeByPath()
3. GetTreeByPath() splits the path by "/" creating empty components
4. This causes the "path component is empty" error
The fix strips the trailing slash before calling GetTreeByPath() to
avoid empty path components, while still using the trailing slash
convention to identify directories.
The Create() method already handles this correctly by appending
".keep" to directory paths, which is why the first export succeeded
but subsequent exports failed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Fix folder tree not updated when folder already exists in repository
When exporting resources and a folder already exists in the repository,
the folder was not being added to the FolderManager's tree. This caused
subsequent dashboard exports to fail with "folder NOT found in tree".
The fix adds the folder to fm.tree even when it already exists in the
repository, ensuring all folders are available for resource lookups.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Revert "Merge remote-tracking branch 'origin/uncomment-unified-migration-code' into cleanup/deprecate-legacy-storage-migration-in-provisioning"
This reverts commit 6440fae3425a2730ee0c50577a515c3049f9655d, reversing
changes made to ec39fb04f28df12f8689413a249c526e61a8e781.
* fix: handle empty folder titles in path construction
- Skip folders with empty titles in dirPath to avoid empty path components
- Skip folders with empty paths before checking if they exist in repository
- Fix unit tests to properly check useResourceStats hook calls with type annotations
* Update workspace
* Fix BootstrapStep tests after reverting unified migration merge
Updated test expectations to match the current component behavior where
resource counts are displayed for both instance and folder sync options.
- Changed 'Empty' count expectation from 3 to 4 (2 cards × 2 counts each)
- Changed '7 resources' test to use findAllByText instead of findByText
since the count appears in multiple cards
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Remove bubbletee deps
* Fix workspace
* provisioning: update error message to reference enableMigration config
Update the error message when provisioning cannot be used due to
incompatible data format to instruct users to enable data migration
for folders and dashboards using the enableMigration configuration
introduced in PR #114857.
Also update the test helper to include EnableMigration: true for both
dashboards and folders to match the new configuration pattern.
* provisioning: add comment explaining Mode5 and EnableMigration requirement
Add a comment in the integration test helper explaining that Provisioning
requires Mode5 (unified storage) and EnableMigration (data migration) as
it expects resources to be fully migrated to unified storage.
* Remove migrate resources checkbox from folder type provisioning wizard
- Remove checkbox UI for migrating existing resources in folder type
- Remove migrateExistingResources from migration logic
- Simplify migration to only use requiresMigration flag
- Remove unused translation keys
- Update i18n strings
* Fix linting
* Remove unnecessary React Fragment wrapper in BootstrapStep
* Address comments
---------
Co-authored-by: Rafael Paulovic <rafael.paulovic@grafana.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
* deps(go): bump the k8s-io group across 2 directories with 2 updates
Bumps the k8s-io group with 1 update in the / directory: [k8s.io/kube-aggregator](https://github.com/kubernetes/kube-aggregator).
Bumps the k8s-io group with 1 update in the /hack directory: [k8s.io/code-generator](https://github.com/kubernetes/code-generator).
Updates `k8s.io/kube-aggregator` from 0.34.2 to 0.34.3
- [Commits](https://github.com/kubernetes/kube-aggregator/compare/v0.34.2...v0.34.3)
Updates `k8s.io/code-generator` from 0.34.2 to 0.34.3
- [Commits](https://github.com/kubernetes/code-generator/compare/v0.34.2...v0.34.3)
---
updated-dependencies:
- dependency-name: k8s.io/kube-aggregator
dependency-version: 0.34.3
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: k8s-io
- dependency-name: k8s.io/code-generator
dependency-version: 0.34.3
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: k8s-io
...
Signed-off-by: dependabot[bot] <support@github.com>
* update all
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Ryan McKinley <ryantxu@gmail.com>
