Skip to content

SLAs activation has unintended side-effects in the target environment #32

@ewingjm

Description

@ewingjm

Describe the bug

By default, all SLAs are deactivated before import and all SLAs are activated after import. This means that there are potentially unintended side-effects of deploying the package. Need to investigate if this logic will still work if it only works on SLAs that are present in the package solution(s). If not possible, then we need to ensure that SLAs are set to the state that they were in prior to the deactivation.

To reproduce

  • Deploy a package to an environment with an inactive SLA. Observe it is active post deployment.

Expected behaviour

SLAs retain the statuses that they had prior to the deployment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions