-
Notifications
You must be signed in to change notification settings - Fork 48
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
Release 10.3 #1414
Comments
1t5j0y
added a commit
that referenced
this issue
Jan 20, 2025
1t5j0y
added a commit
that referenced
this issue
Jan 20, 2025
1t5j0y
added a commit
that referenced
this issue
Jan 20, 2025
1t5j0y
added a commit
that referenced
this issue
Jan 20, 2025
Change made on 10.2 branch and tagged as v10.2.1 |
@mahalakshme , should the self-service reports be enabled in avni-prod after 11.0 release.? |
@himeshr we can disable in 12.0 also, but there should be some way to test in prerelease the ongoing work..I can create a separate card for this may be to disable at the end. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Need:
For reports for organisations for whom Metabase is already setup, we are not sure what can happen. I ve noticed all these 3: Old getting replaced(JSSCP), Old getting merged with new(AKRSP), New not getting created(for many). So we cant be at risk of getting replaced since it depends on how metabase APIs behaves as well.
We had not played this story before because the analyst was unaware that reporting url and api key are set in the prod. Assumed that only for staging it is set. :(
AC:
The text was updated successfully, but these errors were encountered: