You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Matchwas designed to be able to store certs/provisions of multiple team via multiple branches. Nowadays with introduction of mandatory 2fa most developers will have to switch to App Store Connect API .p8 key which more or less get supported in fastlane. However, when working on multiple teams, managing multiple keys is quite a hassle.
I think fastlane needs to support API keys management of some sort. match is already capable of encrypting certs using OpenSSL, so secure storage is out of the question. Maybe match isn't quite the place to store them, but encrypted repo idea may be reused in brand new action?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Match
was designed to be able to store certs/provisions of multiple team via multiple branches. Nowadays with introduction of mandatory 2fa most developers will have to switch to App Store Connect API.p8
key which more or less get supported infastlane
. However, when working on multiple teams, managing multiple keys is quite a hassle.I think
fastlane
needs to support API keys management of some sort.match
is already capable of encrypting certs using OpenSSL, so secure storage is out of the question. Maybematch
isn't quite the place to store them, but encrypted repo idea may be reused in brand newaction
?I want to hear what you guys think.
Beta Was this translation helpful? Give feedback.
All reactions