Why I can swap some settings between deployment slots and I cannot for other settings?
I can note that some of the deployment slots settings of Azure app services can be swapped, but others cannot be swapped.
Do you know why?
azure azure-web-sites asked Nov 29 '18 at 13:08
KrankKrank
337
add a comment |
I can note that some of the deployment slots settings of Azure app services can be swapped, but others cannot be swapped.
Do you know why?
azure azure-web-sites asked Nov 29 '18 at 13:08
KrankKrank
337
See the docs
– Peter Bons
Nov 29 '18 at 13:17
I know that, but why only some settings are allowed and other are not? Any technical justification for that?
– Krank
Nov 29 '18 at 13:30
add a comment |
I can note that some of the deployment slots settings of Azure app services can be swapped, but others cannot be swapped.
Do you know why?
azure azure-web-sites asked Nov 29 '18 at 13:08
KrankKrank
337
I can note that some of the deployment slots settings of Azure app services can be swapped, but others cannot be swapped.
Do you know why?
azure azure-web-sites azure azure-web-sites asked Nov 29 '18 at 13:08
KrankKrank
337
asked Nov 29 '18 at 13:08
KrankKrank
337
asked Nov 29 '18 at 13:08
KrankKrank
337
asked Nov 29 '18 at 13:08
KrankKrank
337
asked Nov 29 '18 at 13:08
KrankKrank
337
337
See the docs
– Peter Bons
Nov 29 '18 at 13:17
I know that, but why only some settings are allowed and other are not? Any technical justification for that?
– Krank
Nov 29 '18 at 13:30
add a comment |
See the docs
– Peter Bons
Nov 29 '18 at 13:17
I know that, but why only some settings are allowed and other are not? Any technical justification for that?
– Krank
Nov 29 '18 at 13:30
See the docs
– Peter Bons
Nov 29 '18 at 13:17
See the docs
– Peter Bons
Nov 29 '18 at 13:17
I know that, but why only some settings are allowed and other are not? Any technical justification for that?
– Krank
Nov 29 '18 at 13:30
I know that, but why only some settings are allowed and other are not? Any technical justification for that?
– Krank
Nov 29 '18 at 13:30
add a comment |
2 Answers
2
active
oldest
votes
First we should understand that slots are primarily meant to be used to deploy new versions of a website real quick. Running (for instance) a staging environment on a slot is not recommended.
These are the settings that, according to the documentation, don't get swapped:
- Publishing endpoints
- Custom Domain Names
- SSL certificates and bindings
- Scale settings
- WebJobs schedulers
If any of these would be swapped, that would mean that your application would break. In more ways than one.
For instance, you would have to change the publishing endpoints for your deployments, since they would have swapped with the slots. This means updating your CI/CD environment every time you swap slots.
The custom domain name that is connected to your production slot would now point to the secondary slot, rendering the swap useless. Because your domain still points to the old version!
If someone managed to reach the new version (which would be hard because the custom domain name still points to the other slot), the SSL certificate (and binding) wouldn't be there. Image that happening to a website that provides a HSTS header.
You can name at least one good reason for each of these settings to not be swapped when swapping slots.
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
add a comment |
We have a number of feature requests in UserVoice for settings to remain sticky to slots and have plans to work on a few of them. Feel free to add your support to the one you're interested in:
https://feedback.azure.com/forums/169385-web-apps
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53539766%2fwhy-i-can-swap-some-settings-between-deployment-slots-and-i-cannot-for-other-set%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
First we should understand that slots are primarily meant to be used to deploy new versions of a website real quick. Running (for instance) a staging environment on a slot is not recommended.
These are the settings that, according to the documentation, don't get swapped:
- Publishing endpoints
- Custom Domain Names
- SSL certificates and bindings
- Scale settings
- WebJobs schedulers
If any of these would be swapped, that would mean that your application would break. In more ways than one.
For instance, you would have to change the publishing endpoints for your deployments, since they would have swapped with the slots. This means updating your CI/CD environment every time you swap slots.
The custom domain name that is connected to your production slot would now point to the secondary slot, rendering the swap useless. Because your domain still points to the old version!
If someone managed to reach the new version (which would be hard because the custom domain name still points to the other slot), the SSL certificate (and binding) wouldn't be there. Image that happening to a website that provides a HSTS header.
You can name at least one good reason for each of these settings to not be swapped when swapping slots.
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
add a comment |
First we should understand that slots are primarily meant to be used to deploy new versions of a website real quick. Running (for instance) a staging environment on a slot is not recommended.
These are the settings that, according to the documentation, don't get swapped:
- Publishing endpoints
- Custom Domain Names
- SSL certificates and bindings
- Scale settings
- WebJobs schedulers
If any of these would be swapped, that would mean that your application would break. In more ways than one.
For instance, you would have to change the publishing endpoints for your deployments, since they would have swapped with the slots. This means updating your CI/CD environment every time you swap slots.
The custom domain name that is connected to your production slot would now point to the secondary slot, rendering the swap useless. Because your domain still points to the old version!
If someone managed to reach the new version (which would be hard because the custom domain name still points to the other slot), the SSL certificate (and binding) wouldn't be there. Image that happening to a website that provides a HSTS header.
You can name at least one good reason for each of these settings to not be swapped when swapping slots.
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
add a comment |
First we should understand that slots are primarily meant to be used to deploy new versions of a website real quick. Running (for instance) a staging environment on a slot is not recommended.
These are the settings that, according to the documentation, don't get swapped:
- Publishing endpoints
- Custom Domain Names
- SSL certificates and bindings
- Scale settings
- WebJobs schedulers
If any of these would be swapped, that would mean that your application would break. In more ways than one.
For instance, you would have to change the publishing endpoints for your deployments, since they would have swapped with the slots. This means updating your CI/CD environment every time you swap slots.
The custom domain name that is connected to your production slot would now point to the secondary slot, rendering the swap useless. Because your domain still points to the old version!
If someone managed to reach the new version (which would be hard because the custom domain name still points to the other slot), the SSL certificate (and binding) wouldn't be there. Image that happening to a website that provides a HSTS header.
You can name at least one good reason for each of these settings to not be swapped when swapping slots.
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
First we should understand that slots are primarily meant to be used to deploy new versions of a website real quick. Running (for instance) a staging environment on a slot is not recommended.
These are the settings that, according to the documentation, don't get swapped:
- Publishing endpoints
- Custom Domain Names
- SSL certificates and bindings
- Scale settings
- WebJobs schedulers
If any of these would be swapped, that would mean that your application would break. In more ways than one.
For instance, you would have to change the publishing endpoints for your deployments, since they would have swapped with the slots. This means updating your CI/CD environment every time you swap slots.
The custom domain name that is connected to your production slot would now point to the secondary slot, rendering the swap useless. Because your domain still points to the old version!
If someone managed to reach the new version (which would be hard because the custom domain name still points to the other slot), the SSL certificate (and binding) wouldn't be there. Image that happening to a website that provides a HSTS header.
You can name at least one good reason for each of these settings to not be swapped when swapping slots.
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
answered Nov 29 '18 at 14:06
rickvdboschrickvdbosch
4,00621526
4,00621526
add a comment |
add a comment |
We have a number of feature requests in UserVoice for settings to remain sticky to slots and have plans to work on a few of them. Feel free to add your support to the one you're interested in:
https://feedback.azure.com/forums/169385-web-apps
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
add a comment |
We have a number of feature requests in UserVoice for settings to remain sticky to slots and have plans to work on a few of them. Feel free to add your support to the one you're interested in:
https://feedback.azure.com/forums/169385-web-apps
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
add a comment |
We have a number of feature requests in UserVoice for settings to remain sticky to slots and have plans to work on a few of them. Feel free to add your support to the one you're interested in:
https://feedback.azure.com/forums/169385-web-apps
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
We have a number of feature requests in UserVoice for settings to remain sticky to slots and have plans to work on a few of them. Feel free to add your support to the one you're interested in:
https://feedback.azure.com/forums/169385-web-apps
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
answered Nov 29 '18 at 17:04
Oded DvoskinOded Dvoskin
1604
1604
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53539766%2fwhy-i-can-swap-some-settings-between-deployment-slots-and-i-cannot-for-other-set%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
See the docs
– Peter Bons
Nov 29 '18 at 13:17
I know that, but why only some settings are allowed and other are not? Any technical justification for that?
– Krank
Nov 29 '18 at 13:30