[wp-meta] [Making WordPress.org] #8030: Introduce different SVN Application passwords for different/high security SVN instances (develop, meta, w.org deploy)

[Making WordPress.org]

#8030: Introduce different SVN Application passwords for different/high security
SVN instances (develop, meta, w.org deploy)
-----------------------------+--------------------
 Reporter:  peterwilsoncc    |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:
Component:  Version Control  |   Keywords:
-----------------------------+--------------------
 This is related to but not quite a duplicate of #5555.

 At present WordPress.org profiles have a single application password used
 for all SVN repositories. For developers using a GitHub action to deploy
 themes or plugins, this is great as it prevents users from recording their
 w.org credentials as secrets on the system.

 As not all SVN instances are equal, it would be helpful if developers
 could create different application passwords for different SVN instances.

 As an example, the `develop.svn.wordpress.org` SVN instance arguably has
 higher security requirements than the `plugins...` or `themes...` SVN
 instance. Using the same application password for all results in the need
 for core committers to add a core commit secret to GitHub for deploying
 their plugins (or, ideally, maintain separate accounts for the different
 purposes).

 Would it be possible to either:

 * allow for different application passwords per SVN instance, falling back
 to the default
 * allow for two application passwords per user account, one for higher
 security SVN instances, one for lower security SVN instances.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8030>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org