sharepoint-sherpa / sherpa Goto Github PK

Some custom content types might depend on out of the box features to be activated. An example is the publishing infrstructure feature to be activated before creating custom article content types.

Since we will be required to run Sherpa multiple times in the same install script(s), the possibility of running Sherpa unattended would be great. E.g
sherpa.exe --url *url* -u *username -p *password* --spo --steps 1,2,3,4,5,6,9 *comma delimited array of steps in installation*
Automatic exit (i.e. option 0) and optional logging would be great, too :)

It's not always a requirement to know the taxonomy term guids. It should be optional to specify them.

"Starting action 4"
"Action 4 finished"

.. and so on!

Would love the possibility to set config path runtime. Otherwise you need to change this everytime you do a pull.

Implement functionality in the lists part of sitehierarchy definition to enable the developer to activate Enterprise Keywords on lists, like f.ex. Pages Library.

If Sherpa doesn't find a wsp in the solutions-folder, it simply states "Done uploading and activating sandboxed solution(s)".
If there are no WSP's in the solution folder, Sherpa should log an error to the console, informing the user that there were no WSP's found (e.g. "No wsp's found in solutions directory %path%").

This is useful when writing custom scripts that run multiple instances of Sherpa, to prevent human error (forgot to copy the wsp to the solutions directory)

If you are using result sources in your CSWP, it is better if you can create those result sources when solution is deployed.

introduction

Sherpa currently support uploading files to one or more document libraries. Sherpa should also learn to support uploading files with content types.

Suggested solution

The suggested solution is as follows

Currently we use the following syntax to define folders which should be uploaded to certain document libraries.

    "ContentFolders": [
        {
            "FolderName": "SiteAssets",
            "ListName": "Site Assets",
            "FolderUrl": "sherpa"
        }
    ]

This solution can be extended to include a manifest file which defines an array with files that has any additional metadata on them (any file not mentioned in the manifest is copied as-is, just a normal file like we have today)

About the manifest

We must suport the explisit properties that is on a File element

https://msdn.microsoft.com/en-us/library/office/ms459213.aspx

I.e.
DocumentTemplateForList = string
DoGUIDFixUp = "TRUE" | "FALSE"
IgnoreIfAlreadyExists = "TRUE" | "FALSE"
Level = Draft
Name = string
NavBarHome = "TRUE" | "FALSE"
Path = string ReplaceContent = "TRUE" | "FALSE"
Type = "Ghostable" | "GhostableInLibrary"
Url = string

As well as the child elements

AllUsersWebPart
Property

Of these, the "Property" element could be replaced with a key-value list. This would be important for provisioning Publishing Page Layouts, display templates etc.

Web part provisioning is something we would also have to support at one point. We should probably have a setting which indicates "replace web part on page", "ignore if web part is on page" or "appen web part to page"

About Display Templates

Display templates are a special breed of files in SharePoint. We would like to have a solution where you can deploy only the .html files and have the .js files created automatically. With csom uploads of files this may actually happen without us having to do anything, but if this is not the case, we may need a "touch after upload" property which indicates that the file will be checked out, in and published again.

At the moment we're limited to one group per file. However, it should be possible to specify one group per inputfile.

Hi!
Ive started to use Sherpa lately on my tenant, when a couple of days ago the the server started returning 403 and specifically: X-MSDAVEXT_Error: 917656; Access denied. Before opening files in this location%2c you must first browse to the web site and select the option to login automatically.

Could you please look into it?

Reasons for this feature

• Features are so "year of the sandbox", remote/CSOM is where it's at. "Sandboxes not recommended anymore"
• Provisioning display templates suck when you have to deploy both html and js files. Would be pretty nice to only provision the html version.

Add property ContentTypes which is a array of strings (content type names). Sherpa should based on this remove and add content types of the list.

Currently only one level is supported

Add verbose output, either using a verbose switch or in a textfile

Should be able to enable items to be rated and which option to have either Likes/Star ratings

Should be able to set following

1. Global navigation as Managed Navigation
2. Set the corresponding termset
3. Should be able to turn on/off default page settings

Requesting the possibility to set up lists in sitehierarchy.json. Preferably with views.

Something like this:
Lists {
Name: "",
Url: "",
TemplateType: "",
Views: []
}

I tried this declarative in our sandboxed solution with a web property bag module. Doesnt seem to work. Would it be possible to add this to Sherpa?

Select a number to perform an operation: 3
Starting setup of site columns and content types
An exception occured: Method not found: 'Void Microsoft.SharePoint.Client.Conten
tTypeCreationInformation.set_Id(System.String)'.
at Sherpa.Library.ContentTypes.Model.GtContentType.GetContentTypeCreationInfo
rmation()
at Sherpa.Library.ContentTypes.ContentTypeManager.CreateContentTypes()
at Sherpa.Installer.InstallationManager.CreateSiteColumnsAndContentTypes()
at Sherpa.Installer.Program.HandleCommandKeyPress(String input)
at Sherpa.Installer.Program.ShowStartScreenAndExecuteCommand()
at Sherpa.Installer.Program.HandleCommandKeyPress(String input)
at Sherpa.Installer.Program.ShowStartScreenAndExecuteCommand()
at Sherpa.Installer.Program.RunApplication()

The export taxonomy should export the taxonomy of a specified taxonomy group, and the output should be in the same json-format as we currently use, including GUIDs.

Url, username osv. has to be input as part of the startup process