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.

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

Enhance SiteDefinition provision - enable provision under the managed path #853

Closed
SubPointSupport opened this issue Jul 9, 2016 · 1 comment
Assignees
Milestone

Comments

@SubPointSupport
Copy link
Contributor

SiteDefinition provision should be supported at the root scope under the managed path.

Currently, the following scenarios are supported and covered in the regression tests:

  • /my-collection
  • /sites/my-collection
  • /custom-path/my-collection

The following is to be implemented:

  • /custom-path/

Community feedback:
https://www.yammer.com/spmeta2feedback/#/threads/show?threadId=733969996

@SubPointSupport SubPointSupport added this to the 2016-07-11 milestone Jul 9, 2016
@SubPointSupport SubPointSupport self-assigned this Jul 9, 2016
@SubPointSupport
Copy link
Contributor Author

Added CanDeploy_Simple_Site_UnderRandomManagedPath_AsRoot test to ensure the mentioned case.
Full set of the tests is under "Regression.Scenarios.Sites"

  • CanDeploy_Simple_Site_UnderRandomManagedPath
  • CanDeploy_Simple_Site_UnderRandomManagedPath_AsRoot
  • CanDeploy_Simple_Site_UnderSitesManagedPath
  • CanDeploy_Simple_Site_WithNullableSecondaryContactLogin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant