-
Notifications
You must be signed in to change notification settings - Fork 302
RN 44371+ 44373 (Ticketing obsolete) #5752
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
AndreRodriguesSkyline
left a comment
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.
I've added a few suggestions.
In general, it would probably be easier to indicate in the text that the ticketing module is obsolete as of version 10.6.0, or when using STaaS, no?
| > | ||
| > - `GRANT CREATE ON ALL KEYSPACES TO <YOUR DATABASE USER/ROLE>;` | ||
| > - `GRANT ALL ON KEYSPACE "SLDMADB" TO <YOUR DATABASE USER/ROLE>;` | ||
| > - `GRANT ALL ON KEYSPACE "sldmadb_ticketing" TO <YOUR DATABASE USER/ROLE>;` |
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.
Starting from RN44417 (the server changes, not yet pushed), the "sldmadb_ticketing" schema is no longer created automatically if it does not exist.
So, maybe add a note indicating that is obsolete from 10.6.0 onwards
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.
We usually don't document release notes as long as the main and feature release versions are still set to TBD, so I'd prefer not to include changes for 44417 within the same pull request. I'll add a reference to 44417 in comment here, so we can add the note with a separate pull request as soon as 44417 is merged.
| #### Modules \> Ticketing Gateway \> UI available | ||
|
|
||
| Permission to access the *Ticketing Gateway* app. | ||
| Permission to access the *Ticketing Gateway* app. Obsolete as of DataMiner 10.5.0 [CU11]/10.6.0. |
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.
Since the ticketing module will no longer be supported from 10.6.0.0 main release onwards, maybe the "DataMiner 10.5.0 [CU11]" can be removed.
The same applies to other locations where this text is present.
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.
RN 44371 and 44373 also mention 10.5.0 [CU11] as main release version, so doesn't this mean that users who stay on the 10.5.0 CU track will also not be able to use Ticketing anymore? I suppose under the hood it will still be available until 10.6.0, but if users can't actually see the app or any of its functionality anymore in Cube and the web apps, I think mentioning 10.5.0 [CU11] here as well would be better.
| # Using the Ticketing Gateway API | ||
|
|
||
| > [!IMPORTANT] | ||
| > The Ticketing Gateway API is obsolete. It is no longer available from DataMiner 10.5.0 [CU11]/10.6.0/10.6.2 onwards. |
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.
This is not related to Cube/Web funcionality, so it will only be deprecated with RN44417 (the same for the files below).
So, if you want, you can say "It is no longer available from 10.6.0 onwards.", and also mention that is not available when using STaaS
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.
If this will only be deprecated with 44417, I think it would be better if we only mention that it is no longer available as soon as 44417 is merged, just in case the versions still change from what is planned.
No description provided.