PR #187 added the possibility to rename CLI actions while retaining the old version as a deprecated alias. Changes in this PR here utilize this development to clear up app-store-connect namespace and group actions interacting with similar resources under action groups. Currently there is a mix of actions like get-reource, list-resources etc and action groups that gather actions for similar resources (apps, beta-groups) such as resources get, resources list etc.
Due to this discrepancy it is hard to add new actions for resources that already have some actions, but do not have their dedicated namespace / action group yet. For example, where to add action that modifies bundle identifiers - should it still go under the root namespace polluting the already messy scope, or should there be another action group for the new action, which would further confuse the command line API?
For now all but one standalone actions that are directly related to a App Store Connect resource were all related to bundle identifiers, certificates, devices or provisioning profiles. New action groups were introduced for those resources to gather all related actions under unified namespace.
[!IMPORTANT]
With all the refactorings carried out in this PR, the public Python API of codemagic.tools.AppStoreConnect remains unchanged.
Renamed actions:
app-store-connect list-builds -> app-store-connect builds list
app-store-connect get-profile -> app-store-connect profiles get
app-store-connect list-profiles -> app-store-connect profiles list
[!NOTE]
Functionality of old actions remains exactly the same with the caveat that invoking a deprecated action will show a warning message.
Examples with screenshots
Calling action with deprecated name
Calling the same action with up-to-date name
Changes to documentation were applied in a follow up PR #387.
PR #187 added the possibility to rename CLI actions while retaining the old version as a deprecated alias. Changes in this PR here utilize this development to clear up
app-store-connectnamespace and group actions interacting with similar resources under action groups. Currently there is a mix of actions likeget-reource,list-resourcesetc and action groups that gather actions for similar resources (apps,beta-groups) such asresources get,resources listetc.Due to this discrepancy it is hard to add new actions for resources that already have some actions, but do not have their dedicated namespace / action group yet. For example, where to add action that modifies bundle identifiers - should it still go under the root namespace polluting the already messy scope, or should there be another action group for the new action, which would further confuse the command line API?
For now all but one standalone actions that are directly related to a App Store Connect resource were all related to bundle identifiers, certificates, devices or provisioning profiles. New action groups were introduced for those resources to gather all related actions under unified namespace.
Renamed actions:
app-store-connect list-builds->app-store-connect builds listapp-store-connect create-bundle-id->app-store-connect bundle-ids createapp-store-connect delete-bundle-id->app-store-connect bundle-ids deleteapp-store-connect get-bundle-id->app-store-connect bundle-ids getapp-store-connect list-bundle-id-profiles->app-store-connect bundle-ids profilesapp-store-connect list-bundle-ids->app-store-connect bundle-ids listapp-store-connect create-certificate->app-store-connect certificates createapp-store-connect delete-certificate->app-store-connect certificates deleteapp-store-connect get-certificate->app-store-connect certificates getapp-store-connect list-certificates->app-store-connect certificates listapp-store-connect list-devices->app-store-connect devices listapp-store-connect register-device->app-store-connect devices registerapp-store-connect create-profile->app-store-connect profiles createapp-store-connect delete-profile->app-store-connect profiles deleteapp-store-connect get-profile->app-store-connect profiles getapp-store-connect list-profiles->app-store-connect profiles listExamples with screenshots
Calling action with deprecated name
Calling the same action with up-to-date name
Changes to documentation were applied in a follow up PR #387.