Since we are working on #2917 and #2919 (and more to come as we move along) we should introduce a new type of command class. The PPCommand. That base class should have the following:
- logic to handle different environments
- handle all Power Platform services based on this environment
The PowerShell samples use a -Endpoint parameter within the Add-PowerAppsAccount cmdlet (and picks the default production endpoint when none is specified). Given the nature of the CLI I feel that we should use a slightly different approach. For me it makes the most sense to use the m365 cli config set and add an additional parameter there called PowerPlatformEndpoint. Should be a string value with a few options (Valid options are "dod", "prod","preview","tip1", "tip2", "usgov", or "usgovhigh".)
@pnp/cli-for-microsoft-365-maintainers how do you feel about that?
Since we are working on #2917 and #2919 (and more to come as we move along) we should introduce a new type of command class. The
PPCommand. That base class should have the following:The PowerShell samples use a
-Endpointparameter within theAdd-PowerAppsAccountcmdlet (and picks the default production endpoint when none is specified). Given the nature of the CLI I feel that we should use a slightly different approach. For me it makes the most sense to use them365 cli config setand add an additional parameter there calledPowerPlatformEndpoint. Should be a string value with a few options (Valid options are "dod", "prod","preview","tip1", "tip2", "usgov", or "usgovhigh".)@pnp/cli-for-microsoft-365-maintainers how do you feel about that?