-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancements: m365 pa app list #2872
Comments
@pnp/cli-for-microsoft-365-maintainers if would implement the same logic for as we did for Flow we would have to make the environment property required. However that would introduce a breaking change. I opt for implementing it as an optional parameter to keep current scripts and scenario's in place, and as part of our efforts for V4/V5 we could introduce a single |
What if we introduced the |
Great idea, agree.
Not 100% sure if we can deprecate both (
Agree |
That's odd. Ideally, we'd figure it out to avoid offering our users ambiguous choices. Can you see any differences in the data you retrieve from these different APIs? |
Enhance the
m365 pa app list
command with a option to specify the environment using following option:-e, --environment [environment]
Implement in code using the following statement in the get request:
https://{powerAppsEndpoint}/providers/Microsoft.PowerApps/scopes/admin/environments/{environment}/)'
Enhance the
m365 pa app list
command with a option to retrieve data as admin :--asAdmin
Implement in code using the following statement in the get request:
../providers/Microsoft.PowerApps/scopes/admin/..
The text was updated successfully, but these errors were encountered: