Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement more PowerPlatform commands #3670

Open
29 of 92 tasks
appieschot opened this issue Sep 13, 2022 · 22 comments
Open
29 of 92 tasks

Implement more PowerPlatform commands #3670

appieschot opened this issue Sep 13, 2022 · 22 comments
Assignees
@appieschot
Labels
epic work in progress

Comments

@appieschot
Copy link
Member

appieschot commented Sep 13, 2022 •
edited
Loading

With the advent of hacktober fest and our ambition to create a set of new good first issues following a list of commands we need for the Power Platform, a first 'shot' at it below. Let's gather additional requests in this issue and create new issues based on them.

Good first issues

Issues that should be relatively easy since we already have some of the stuff in place

The following are straightforward but require a little bit of research for the exact URL's, with some investigation from our side we can make them as 'good first issue', ordered by amount of work to spec:

Random ideas

Power Pages

Pipelines

Updates

  • m365 pp environment remove
  • m365 pp environment add

Needs research to execute more complex Dynamic Queries first

  • m365 pp data export (see pac data export)
  • m365 pp data import (see pac data import)
  • m365 pp connector list (see pac connector list)
  • m365 pp connector get (see `pac connector download)
  • m365 pp dataverse query -> we need to figure out if we do a generic query and pass the table + query or if we need other advanced scenario's. See https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/query-data-web-api
  • m365 pp website webfile preview
  • m365 pp website webfile sync

Needs research for what API to use (most likely easy as it is part of the PowerShell or PAC)

V2 release

  • pp solution export
  • pp solution import

V3 release
@martinlingstuyl
Copy link
Contributor

What about pp solution export and pp solution import?

@appieschot
Copy link
Member Author

@martinlingstuyl would be a great addition, but already part of the pac cli, so my vote would be to prioritize them last and focus on the stuff that's not there yet.

@martinlingstuyl
Copy link
Contributor

That's fine with me!

@martinlingstuyl
Copy link
Contributor

Adding them to the epic would still be good though

@appieschot
Copy link
Member Author

Done :D

@appieschot appieschot self-assigned this Sep 27, 2022
@ryanspain
Copy link

I'd love to see commands like the below to improve the inner dev loop when working on web resources. This would save having to use other [still great] tools like spkl from Scott Durow and XrmToolBox plugins.

  • pp dataverse webresource list
  • pp dataverse webresource get
  • pp dataverse webresource export
  • pp dataverse webresource import

Each with options to provide a --solution and --environment amongst other options.

Unsure whether it would be better placed under pa webresource list, given web resources are generally used in model-driven Power Apps. Or possible via pa solution webresource [list/get/export/import] given that pa solution uses a solution project in the current directory.

Thoughts? I'd love to contribute to the design/dev if you think there would be interest.

@appieschot
Copy link
Member Author

@ryanspain that totally makes sense, feels like we should put them under our dataverse command as from what I know a web resource is stored in the dataverse database and thus feels 'correct' to group under there.

We would love to have them specced. I have added them to the epic and feel free to spec out!.

@appieschot appieschot mentioned this issue Oct 10, 2022
Closed
@appieschot
Copy link
Member Author

Note to self: https://learn.microsoft.com/en-us/power-automate/web-api we can use this to retrieve flows as well :)

@appieschot
Copy link
Member Author

@nicodecleyre since you already did some awesome work with #4174 would you mind giving speccing the get and remove versions a stab as well? Looks like our full list is almost complete so would be awesome!

@nicodecleyre
Copy link
Contributor

@nicodecleyre since you already did some awesome work with #4174 would you mind giving speccing the get and remove versions a stab as well? Looks like our full list is almost complete so would be awesome!

Done!

@milanholemans
Copy link
Contributor

@nicodecleyre since you already did some awesome work with #4174 would you mind giving speccing the get and remove versions a stab as well? Looks like our full list is almost complete so would be awesome!

Done!

* [ ]  [New command: `m365 pp aibuildermodel get` #4325](https://github.com/pnp/cli-microsoft365/issues/4325)

* [ ]  [New command: `m365 pp aibuildermodel remove` #4326](https://github.com/pnp/cli-microsoft365/issues/4326)

Included them in the specs of this epic

@milanholemans
Copy link
Contributor

Hi @appieschot, are you still planning to spec out more commands?

@Adam-it
Copy link
Contributor

Adam-it commented Aug 10, 2024

@appieschot pretty please 🙏🙂

@Jwaegebaert
Copy link
Contributor

@appieschot pretty pretty pretty please 😉

@appieschot
Copy link
Member Author

appieschot commented Aug 19, 2024 via email

@appieschot
Copy link
Member Author

How do we feel about adding an alias to the chatbot commands and provide them with copilot as well as to align better with current naming :)?

@milanholemans
Copy link
Contributor

How do we feel about adding an alias to the chatbot commands and provide them with copilot as well as to align better with current naming :)?

Or should we rename the commands? Is "chatbot" still used?

@appieschot
Copy link
Member Author

@milanholemans I am not 100% sure, I see a lot of customers still referring it to PVA so it might be a matter of time, I think MS is not using Chatbot anymore, but business usually takes a while to catch-up :)

@appieschot
Copy link
Member Author

Oh and would it make sense to close out this epic and start a new one with all our new ideas, or keep working in this one :D. Just specced out two commands and added more ideas to this epic 🤷.

@milanholemans
Copy link
Contributor

If it's Power Platform related, I'd say let's use this epic.

@Adam-it
Copy link
Contributor

Adam-it commented Aug 21, 2024

How do we feel about adding an alias to the chatbot commands and provide them with copilot as well as to align better with current naming :)?

I agree on creating an alias and wait a bit before we totally remove chat or in favor of copilot

@appieschot
Copy link
Member Author

Created issue #6261 to finalize the discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@appieschot appieschot

Labels
epic work in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@martinlingstuyl @ryanspain @milanholemans @appieschot @nicodecleyre @Jwaegebaert @Adam-it