We should add the full schema functionality to CLI/WebUI
Metadata Update from @spichugi: - Issue assigned to spichugi
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1623633 - Custom field type adjusted to None - Custom field version adjusted to None
I think we should reserve schema modification to cli as it's a pretty complex topic, and not one to go into lightly. We'll want a solid CLI first before we think about a ui. Is that reasonable?
We had the functionality in the console already: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/administration_guide/index#Managing_Attributes
And Mark did put the template code in JS and HTML for this (it looks the same as in console) I think we can keep it. It was there and I don't see any harm. Though we can put a warning somewhere about the seriousness. What do you think?
@mreynolds ?
https://pagure.io/389-ds-base/pull-request/49931
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
I think we should reserve schema modification to cli as it's a pretty complex topic, and not one to go into lightly. We'll want a solid CLI first before we think about a ui. Is that reasonable? We had the functionality in the console already: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/administration_guide/index#Managing_Attributes And Mark did put the template code in JS and HTML for this (it looks the same as in console) I think we can keep it. It was there and I don't see any harm. Though we can put a warning somewhere about the seriousness. What do you think? @mreynolds ?
We had the functionality in the console already: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/administration_guide/index#Managing_Attributes And Mark did put the template code in JS and HTML for this (it looks the same as in console) I think we can keep it. It was there and I don't see any harm. Though we can put a warning somewhere about the seriousness. What do you think? @mreynolds ?
@firstyear The way we are doing this is we get the CLI working first, then we add it to the UI. This does need to be in the UI. I see no reason not to add this to UI once the CLI is ready. @spichugi please continue working on this.
https://pagure.io/389-ds-base/pull-request/49957
https://pagure.io/389-ds-base/pull-request/49966
Metadata Update from @spichugi: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2987
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Log in to comment on this ticket.