Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
REGEX Help for submit.cfg
BBeaver
Hi guys,
I'm a little REGEX-challenged, so please excuse my ignorance. We have always used extension-specific references in our submit.cfg for all workareas in a branch, and I am trying to simplify the process. I would now like to apply the permissions to all files submitted by workarea. Here's an example of how we currently apply permissions at the branch and extension level from our submit.cfg (and it works):
/main/Release3/WORKAREA/.*
{
.*\.gif$ { setaccess = {C1APP099\Common:all, Everyone:RX} }
}
Below is what I am try to accomplish, but doesn't work:
/main/Release3/WORKAREA/test_WA/.*
{
.* { setaccess = {C1APP099\Common:all, Everyone:RX} }
}
Basically, I would like to assign the Common and Everyone groups to all files submitted from the test_WA workarea. However, every time I add a reference to the workarea in the first line, I'm not getting any permission changes. Any suggestions to tweak my REGEX would be greatly appreciated.
Find more posts tagged with
Comments
Freedom
Have you tried to put $ at the end? i.e.:
.*$ { setaccess = {C1APP099\Common:all, Everyone:RX} }
BBeaver
Yes, that doesn't seem to help. It appears that it is tied to my having the workarea name in the first line. Whenever I remove the workarea reference, it works fine with or without the $.
Adam Stoller
First of all - DO NOT TRY TO SET DIFFERENT PERMISSIONS BASED ON WORKAREA -- this is not how the product was designed to work and will cause you no end of grief trying to get it to work and maintain it over the long run.
Secondly - I believe that submit.cfg is processed in a top-down fashion - so if you wanted certain *directories* to have different access rights than all the rest - you would need to specify those specific directory settings *above* the generic directory settings (likewise for files) - also I believe you need to specify directory regex's *before* file regexs since file regexes match "everything" and directory regexs would only match the directory (utilizing '$' to anchor the end of the path)/
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com