#!/usr/bin/env python # ============================================================================== # Copyright and license info is available in the LICENSE file included with # the Server Deployment Package (SDP), and also available online: # https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE # ------------------------------------------------------------------------------ # # This script emails the owners of each group with instructions on how to validate the membership of the groups they own. # import os, sys import smtplib from email.mime.text import MIMEText import sdputils if len(sys.argv) > 1: # see params above SDP_INSTANCE = str(sys.argv) else: SDP_INSTANCE = '1' utils = sdputils.SDPUtils(SDP_INSTANCE) config = utils.config p4 = utils.p4 utils.login() fromAddr = config.get('administrator') replyToAddr = '' mailSMTPhost = config.get('mailhost') mailSMTPport = int(config.get('mailport')) mailsecure = int(config.get('mailsecure')) if mailsecure: mailUser = config.get('mailuser') mailPass = config.get('mailpass') def email_owner(group, owner): message = """ You are the owner of this group: %s As the owner, you are expected to audit the group membership on a quarterly basis. To edit/review the group membership, open a command prompt and run: p4 group -a %s Regards, Perforce Admin Team %s """ for line in os.popen("p4 -ztag user -o %s" % owner): if line.startswith(r"... Email"): owner_email = line.lstrip(r"... Email ") break msg = MIMEText(message % (group, group, fromAddr)) msg['Subject'] = "%s Group Audit Reminder" % group msg['From'] = fromAddr if (len(replyToAddr)): msg.add_header('reply-to', replyToAddr) msg['To'] = owner_email try: # print("Sending mail to: %s" % owner_email) s = smtplib.SMTP(mailSMTPhost, mailSMTPport) # Uncomment below for secure connections # s.starttls() # s.login(mailUser, mailPass) s.sendmail(msg['From'], msg['To'], msg.as_string()) s.quit() except smtplib.SMTPException: print("Error: unable to send email to %s." % msg['To']) def main(): for group in os.popen("p4 groups").readlines(): owners = 0 group = group.rstrip() for line in os.popen("p4 -ztag group -o %s" % group): if line.startswith(r"... Users"): break if line.startswith(r"... Owners"): owners = 1 owner = line.split() email_owner(group, owner) if not owners: print("%s,No owner." % group) if __name__ == "__main__": main()
|#2||24675||russell_jackson||Fixed bugs in sdputils.py and scripts using it. Converted to standard 2 space spacing, removed copyright stuff.|
Branched a Unix only version of the SDP.
Removed extra items to create a cleaner tree.
Moved a few items around to make more sense without Windows in the mix.
|#5||22337||russell_jackson||Added +x to file types.|
Routine merge down to dev from main using:
p4 merge -b perforce_software-sdp-dev
Routine merge to dev from main using:
p4 merge -b perforce_software-sdp-dev
Normalized P4INSTANCE to SDP_INSTANCE to get Unix/Windows
implementations in sync.
1. Things that interact with SDP in both Unix and Windows
environments shoudn't have to account for this obscure
SDP difference between Unix and Windows. (I came across
this doing CBD work).
2. The Windows and Unix scripts have different variable
names for defining the same concept, the SDP instance.
Unix uses P4INSTANCE, while Windows uses SDP_INSTANCE.
3. This instance tag, a data set identifier, is an SDP concept.
I prefer the SDP_INSTANCE name over P4INSTANCE, so I prpose
to normalize to SDP_INSTANCE.
4. The P4INSTANCE name makes it look like a setting that might be
recognized by the p4d itself, which it is not. (There are other
such things such as P4SERVER that could perhaps be renamed as
a separate task; but I'm not sure we want to totally disallow
the P4 prefix for variable names. It looks too right to be wrong
in same cases, like P4BIN and P4DBIN. That's a discussion for
another day, outside the scope of this task).
* Fixed a bug in the Windows 2013.3 upgrade script that
was referencing undefined P4INSTANCE, as the Windows
environment defined only SDP_INSTANCE.
* Had P4INSTANCE been removed completely, this change would
likely cause trouble for users doing updates for existing
SDP installations. So, though it involves slight technical debt,
I opted to keep a redundant definition of P4INSTANCE
in p4_vars.template, with comments indicating SDP_INSTANCE should be
used in favor of P4INSTANCE, with a warning that P4INSTANCE
may go away in a future release. This should avoid unnecessary
* In mkdirs.sh, the varialbe name was INSTANCE rather than
SDP_INSTANCE. I changed that as well. That required manual
change rather than sub/replace to avoid corrupting other similar
varialbe names (e.g. MASTERINSTANCE).
This is a trivial change technically (a substitute/replace, plus
tweaks in p4_vars.template), but impacts many files.
Routine merge down from main -> dev.
Trivial merges, all resolved with 'p4 resolve -as.'
|#1||13561||russell_jackson||New maintenence script to email a reminder to group owners to audit their groups.|