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

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

Open
ewingjm opened this issue Jan 29, 2021 · 0 comments
Open
Labels
bug Something isn't working

Comments

@ewingjm
Copy link
Member

ewingjm commented Jan 29, 2021

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.

@ewingjm ewingjm added the bug Something isn't working label Jan 29, 2021
@tdashworth tdashworth added this to To do in CSD Microsoft - Q1 2021 via automation Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

1 participant