Skip to content

docs(serverless): add Versioning and rollback section #3803

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Oct 9, 2024
Merged

docs(serverless): add Versioning and rollback section #3803

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b8928f3
docs(serverless): add section Versioning and rollback in function and…
Bemilie Oct 7, 2024
1f52c6e
fix: review changes
Bemilie Oct 8, 2024
370517e
docs(SRV): update
SamyOubouaziz Oct 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions serverless/containers/reference-content/containers-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,3 +86,12 @@ For example, if you build an image using an ARM CPU, such as Apple Silicon M ser
You must ensure that you build your image to target `amd64` architecture, to acheive this there are multiple solutions:
* You can use the following Docker command: `docker buildx build --platform linux/amd64 .`, or
* You can use an Instance with `amd64` architecture to run your builds.

## Versioning and rollback

Scaleway Containers do not currently support versioning or automatic rollback mechanisms.
However, in the event of a failed deployment, the previously deployed version of the container will continue to handle
incoming requests for up to 24 hours. After this period, the container in error will be deleted, and requests will no
longer be served until a successful deployment is made. This ensures temporary service continuity, but it is important
to monitor and resolve deployment issues promptly, as the fallback is not intended to provide long-term version control
or rollback capabilities.
9 changes: 9 additions & 0 deletions serverless/functions/reference-content/functions-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,3 +55,12 @@ To ensure the proper functioning of the product, we restrict the use of certain
* **465**: Due to potential abuse (spam), no outbound traffic is allowed through this port, except from Scaleway Transactional Email SMTP servers.
* Reserved environment variables:
* `SCW_*`: Reserved for product configuration (for example: token validation).

## Versioning and rollback

Scaleway Functions do not currently support versioning or automatic rollback mechanisms.
However, in the event of a failed deployment, the previously deployed version of the function will continue to handle
incoming requests for up to 24 hours. After this period, the function in error will be deleted, and requests will no
longer be served until a successful deployment is made. This ensures temporary service continuity, but it is important
to monitor and resolve deployment issues promptly, as the fallback is not intended to provide long-term version control
or rollback capabilities.