Epic Goal

Currently we ship a Grafana-Dev and a Grafana-Prod Instance.
We might not need Grafana-Dev at all, but direcltly allow changes to the prod instances.

Grafana-Dev seems uncessary and removing it would help to clean up the code base

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

• proper risk analysis
• deprecation necessary?
• do some customers use some development flow which involves the dev-instance?
• this is just a minor effort
• document how to do changes directly in prod

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.