Hello community,
I read the details about seamless deployments and think it is a fantastic process improvement. Given a choice between "outage" and "no outage", the "no outage" option is an obvious choice.
It seems like this should just be the default method of deployments. Is there a negative aspect of seamless deployments that I'm overlooking?
Solved! Go to Solution.
I cannot think of any consequences besides what is noted in the docs: if the new revision has a different basepath, the previous revision will not be un-deployed.
Also, if you are using the maven deploy plugin, you can control this behavior using the following in your profile:
<profile> <id>prod</id> <properties> ... <apigee.options>override</apigee.options> <apigee.override.delay>5</apigee.override.delay> </properties> </profile>
I cannot think of any consequences besides what is noted in the docs: if the new revision has a different basepath, the previous revision will not be un-deployed.
Also, if you are using the maven deploy plugin, you can control this behavior using the following in your profile:
<profile> <id>prod</id> <properties> ... <apigee.options>override</apigee.options> <apigee.override.delay>5</apigee.override.delay> </properties> </profile>
User | Count |
---|---|
7 | |
2 | |
2 | |
2 | |
1 |