Grafana: 6. Change the configuration

This documentation is part of the Automate with the CLI guide. You can view the complete guide here: Start Grafana, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI.

👋 Welcome to the Stackhero documentation!

Stackhero provides you with a ready-to-use Grafana cloud environment, designed for rapid deployment and reliable performance:

• Unlimited users, dashboards, and alerts: scale your monitoring as required, with no artificial restrictions.
• A dedicated SMTP email server is included, allowing you to send as many notifications as you need, with no quotas to monitor.
• One-click plugin installation makes it easy to add new features to Grafana.
• Built-in SSO support for GitLab, GitHub, Google, and any generic OAuth2 provider. User management remains straightforward and secure.
• One-click updates ensure your Grafana instance stays up to date, with no downtime or maintenance headaches.
• Use your own custom domain with automated HTTPS provisioning for secure, branded access (for example, https://grafana.your-company.com).
• High performance and enhanced security come as standard, running on your own private, dedicated infrastructure.

Get started more quickly and save time on setup: a secure Grafana cloud hosting instance is ready in around 5 minutes.

You can review an example configuration schema and then apply your own settings. When you update the configuration, the service may restart to apply the changes.

# View the configuration schema and an example for your service
stackhero service-configuration-example --service=svc-xxxxxx

# Apply a custom configuration (the service restarts if necessary)
stackhero service-configuration-set \
  --service=svc-xxxxxx \
  --configuration='{ "...": "..." }'

# Wait for the new configuration to be applied
stackhero service-wait-for --service=svc-xxxxxx

That is it. You have now seen the full lifecycle: start a service, retrieve its credentials, and reconfigure it, all in a scriptable, automated manner. To explore further, refer to the full CLI documentation, which also covers the non-interactive STACKHERO_TOKEN authentication demonstrated here.