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

Migrate configurations during sn6-sn7 upgrade #339

Closed
tusmester opened this Issue Apr 13, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@tusmester
Member

tusmester commented Apr 13, 2018

Config sections changed since sn6 significantly.

  • Web.config
  • Tools\SnAdminRuntime.exe.config

The step can be something like this:

<?xml version="1.0" encoding="utf-8"?>
<Package>
  ...
  <Steps>
    <EditConfiguration>
      <Move>
        <Element sourceSetion="section1"
                 targetSection="sensenet/section2" />
        <Element sourceSetion="appSettings"
                 sourceKey="asdf"
                 targetSection="sensenet/section3"
                 default="42" />
        <Element sourceSetion="appSettings"
                 sourceKey="LuceneActivityTimeoutInSeconds"
                 targetSection="sensenet/indexing"
                 targetKey="IndexingActivityTimeoutInSeconds" />
        ...
      </Move>
      <Delete>
        <Element section="appSettings"
                 key="RestoreIndex" />
        ...
      </Delete>
    </EditConfiguration>
  </Steps>
</Package>```

@tusmester tusmester added this to the Sprint 156 milestone Apr 13, 2018

@tusmester tusmester modified the milestones: Sprint 156, Sprint 157 Apr 18, 2018

@kavics kavics self-assigned this Apr 19, 2018

@tusmester tusmester modified the milestones: Sprint 157, Sprint 158 May 2, 2018

@tusmester

This comment has been minimized.

Member

tusmester commented May 16, 2018

Make sure that if the moved key exists in the target section, we do not end up with duplicate keys.

@tusmester tusmester modified the milestones: Sprint 158, Sprint 159 May 16, 2018

@kultsar kultsar closed this May 23, 2018

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