-
Notifications
You must be signed in to change notification settings - Fork 29
Migrate self-hosted grafana to azure managed grafana #6304
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
base: main
Are you sure you want to change the base?
Conversation
…t/dnceng into haruna/managed-grafana-new
| dependsOn: ProvisionGrafana | ||
| displayName: 'Setup Grafana API Token' | ||
| variables: | ||
| GrafanaEndpoint: $[ dependencies.ProvisionGrafana.outputs['ExportGrafanaInfo.GrafanaEndpoint'] ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why use this method with ExportGrafanaInfo instead of parameter variables (like e.g. parameters.AMGGrafanaKeyVault)?
| Write-Host "Granting pipeline service principal Grafana Admin role..." | ||
|
|
||
| $workspaceName = "${{ parameters.AMGGrafanaWorkspaceName }}" | ||
| $rgName = "monitoring-managed" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider making this a parameter as well. It can have this as the default value. Then all the tweakable variables will be up at the top in the same area.
|
What testing has this seen? |
I created a pipeline in the internal repo to test the changes. |
No description provided.