-
Notifications
You must be signed in to change notification settings - Fork 74
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
Make PDAdmin calls Idempotent #10
Comments
FYI - the code developed for this has issues with very large sets of pdadmin commands. Hence put on hold. |
Hi, is there any updates on this? We would love to have idempotent pdadmin calls :) |
The code I developed did not scale very well. So this is on hold. |
Here is the code if anyone wants to see if they can come up with a better solution:
|
Any updates on this issue ? |
The code I provided works - but it breaks when there are many thousands of pdadmin commands to be run at a time. Hence has been on the backburner. |
Hi, this is my approach. It doesn't cover all the idempotent requirements, but it is simple enough to be readable and maintainable, and potentially extended to make it all idempotent. playbooks/isam.yml- hosts: isam
roles:
- lib/ibm/isam
vars:
ISAM:
policy:
- name: 'POP: forbidden'
check: pop show forbidden
set:
- pop create forbidden
#
- pop modify forbidden set description "Never allow access to this object"
- pop modify forbidden set ipauth anyothernw forbidden
- pop modify forbidden set audit-level all
#
- pop attach /WebSEAL/example.org/dynurl/forbidden forbidden
- name: 'POP: anonymous'
check: pop show anonymous
set:
- pop create anonymous
#
- pop modify anonymous set description "Anonymous access"
- pop modify anonymous set ipauth anyothernw 0
- pop modify anonymous set audit-level none
#
- pop attach /WebSEAL/example.org anonymous
- pop attach /WebSEAL/example.org/favicon.ico anonymous
- pop attach /WebSEAL/example.org/index.html anonymous
|
I saw this yesterday and read it a couple more times today - I am not sure how it is idempotent, I mean by avoiding a change if it is already in place? Perhaps I need to run the logic to understand it better. FYI - my code above works, it fails when there are thousands of pdadmin commands to process. So the problem is scale, for me. |
This is a work in progress. Each PDAdmin command provided will be parsed, the ones that will update will have a corresponding PDADmin command crafted to see if that updated was already done. If updates are already in place then those PDADmin commands will be commented out before execution and the output returned.
The text was updated successfully, but these errors were encountered: