COU-354 - Ignoring the access.config courier file if it isn't used anyways

Created by Claus Jensen 21 Jun 2016, 08:19:22 Updated by Morten Christensen 21 Jun 2016, 11:15:43

Tags: Unscheduled

The access.config courier file causes deploy to fail if it was generated at some point and left in the site. We need to somehow ignore it so deploys will run anyway.

Need a broken site to test this with (Rune should let Claus know when he has one)

Comments

Claus Jensen 21 Jun 2016, 09:58:56

PR: https://github.com/umbraco/UmbracoDeploy/pull/46

I've changed it so we deserialize with the correct type even though we may not need the deserialized data afterwards (instead of just returning null as I wasn't sure if this would cause any trouble elsewhere).

Then if we're expecting a guid identifier (this would based on umbraco version) - and we can't parse the identifier as a guid (meaning it is an access.config) - we ignore it at this step as this is also where we usually "reject" items.


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 2.52.8

Due in version: 2.52.9

Sprint: Sprint 36

Story Points:

Cycle: