Currently all the data objects in the Python API can only be created from their JSON representations. We should also have a similar approach for handling xml representation of the data objects. It would enable users to fetch the data objects, especially the ones which are sent back to the server as payload in the request (All *Request classes in cert.py and key.py ) to be fetched using CLI and load them using the python API to make any more additions and submit to the server.
Example: To modify an existing profile, the following operations can be done:
pki <agent_authentication> ca-profile-show <profile_name> --output <file_path>
Using the client(python code): profile_data = Profile.load_from_xml(<file_path>) profile_data.add_input(<ProfileInput object>) profile_data.remove_input(<profile_input_id>) ... profile_client.modify_profile(profile_data)
Would like to suggest to be part of 10.3 bucket.
Rewriting the example with better format.
profile_data = Profile.load_from_xml(<file_path>)
profile_data.add_input(<ProfileInput? object>)
profile_data.remove_input(<profile_input_id>) ...
profile_client.modify_profile(profile_data)
Moving to proposed Milestone: 10.3 per suggestion
Metadata Update from @kaskahn: - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1625
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, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.