-
Notifications
You must be signed in to change notification settings - Fork 41
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
pac solution sync does not bring down Plugin Package into the source #1073
Comments
Experiencing the same issue! Workaround for now is running pac solution export and pac solution unpack |
I resolved the issue - the problem was that I originally had started with a regular plugin assembly, and the unpacked solution still had references to the old plugin assembly and step with the same name prior to converting it to a Plugin Package. I had to manually remove the plugin assembly and plugin step root components in the solution.xml file, and delete the plugin step under the sdkprocessingstep folder. Reran the sync which pulled it down correctly. I imagine it shouldn't be an issue if you started with a plugin package to begin with. |
Thanks for that @chrispiasecki! I was hopeful that it would resolve it with these steps but still not working for me.... I only get the SdkMessageProcessingSteps. Do you mind reopening this bug? It would avoid me creating a new one... |
Same here.
|
@ericregnier tell please what map.xml you use in your workaround |
Describe the bug
When using
pac solution sync
, a Plugin Package is not being synced and missing in the unpacked solution directory.To Reproduce
Steps to reproduce the behavior:
pac solution clone
pac solution sync -p Both -a
pluginpackages
directory is not present. The plugin step registered against the plugin package/assembly is present in theSdkMessageProcessingSteps
directory.Expected behavior
Plugin Packages should always be synced.
Desktop (please complete the following information):
Additional context
Latest PAC CLI version (1.36.3+g76bcfe6) installed at the time of writing
The text was updated successfully, but these errors were encountered: