From 11c7a6e5ed69c0f291eb03fa3e08a0d8b2965410 Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Thu, 25 Sep 2025 15:55:29 +0200 Subject: [PATCH 1/3] docs(add): saml endpoints --- macros/audit-trail/iam-endpoints.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/macros/audit-trail/iam-endpoints.mdx b/macros/audit-trail/iam-endpoints.mdx index f52d6b8352..13ef040d94 100644 --- a/macros/audit-trail/iam-endpoints.mdx +++ b/macros/audit-trail/iam-endpoints.mdx @@ -40,4 +40,11 @@ macro: adt-iam-endpoints - DeletePolicy (`DELETE /iam/v1alpha1/policies/{policy_id}`) - ClonePolicy (`POST /iam/v1alpha1/policies/{policy_id}/clone`) - SetRules (`PUT /iam/v1alpha1/rules`) + - AddSamlCertificate (`POST /iam/v1alpha1/`) + - CreateJWT (`POST /iam/v1alpha1/`) + - DeleteJWT (`DELETE /iam/v1alpha1/`) + - DeleteSaml (`DELETE /iam/v1alpha1/`) + - DeleteSamlCertificate (`DELETE /iam/v1alpha1/`) + - EnableOrganizationSaml (``) + - UpdateSaml (`PATCH /iam/v1alpha1/`) \ No newline at end of file From 5d44c4771cfa98abc4fdac218bbdc38137568053 Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Wed, 1 Oct 2025 11:12:13 +0200 Subject: [PATCH 2/3] docs(add): migration methods & tools doc --- pages/use-cases/migration-methods/index.mdx | 63 +++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 pages/use-cases/migration-methods/index.mdx diff --git a/pages/use-cases/migration-methods/index.mdx b/pages/use-cases/migration-methods/index.mdx new file mode 100644 index 0000000000..6e2fc572f3 --- /dev/null +++ b/pages/use-cases/migration-methods/index.mdx @@ -0,0 +1,63 @@ +--- +title: Migration methods and tools +description: Discover the available migration methods and tools to move your infrastructure to Scaleway and develop your projects. +--- + +## Migration methods and tools + +Migrating to the cloud can take different forms depending on your infrastructure, business goals, and long-term strategy. + +Choosing the right method depends on your priorities: speed, cost, flexibility, or long-term innovation. Below are the main migration methods you can choose from when planning for your migration. + + + + + Lift and shift is the most direct migration strategy. Applications and workloads are moved “as-is” from their current environment to the cloud, with minimal to no modifications. It focuses on speed and simplicity rather than optimization. + + **When to use it** + + - You need to migrate quickly, with minimal downtime. + - Your priority is moving out of on-premises infrastructure or another provider. + - You want a foundation in the cloud before making further optimizations. + + + + Replatforming involves making minor adjustments to workloads during migration to take advantage of cloud features, without fully redesigning the application. + + **When to use it** + + - You want to reduce operational complexity. + - Your goal is to gain some cloud-native benefits (e.g. automated scaling, managed storage). + - Your applications are stable but can benefit from optimizations. + + + + Refactoring goes further by modifying the application code to better align with cloud-native services and architectures. + + **When to use it** + + - You want to modernize applications for better scalability and resilience. + - You want to integrate managed services (databases, event-driven systems, etc.). + - Your current architecture is functional but starting to limit growth. + + + + Rearchitecting means redesigning applications from the ground up to fully leverage cloud-native principles, such as microservices, serverless, and distributed computing. + + **When to use it** + + - Legacy systems limit innovation and agility. + - You want to build for long-term scalability and resilience. + - You need to support advanced workloads like AI, big data, or edge computing. + + + + Instead of migrating an existing system, some organizations choose to replace applications with new cloud-native solutions or SaaS alternatives. + + **When to use it** + + - The existing system is outdated or too costly to adapt. + - SaaS or managed solutions provide more value. + - You want to simplify infrastructure and focus resources on core business goals. + + \ No newline at end of file From 0396af1deca2374815647458dcdb61f66c88cc78 Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Wed, 1 Oct 2025 11:14:21 +0200 Subject: [PATCH 3/3] docs(fix): rm saml doc --- macros/audit-trail/iam-endpoints.mdx | 7 ------- 1 file changed, 7 deletions(-) diff --git a/macros/audit-trail/iam-endpoints.mdx b/macros/audit-trail/iam-endpoints.mdx index 13ef040d94..f52d6b8352 100644 --- a/macros/audit-trail/iam-endpoints.mdx +++ b/macros/audit-trail/iam-endpoints.mdx @@ -40,11 +40,4 @@ macro: adt-iam-endpoints - DeletePolicy (`DELETE /iam/v1alpha1/policies/{policy_id}`) - ClonePolicy (`POST /iam/v1alpha1/policies/{policy_id}/clone`) - SetRules (`PUT /iam/v1alpha1/rules`) - - AddSamlCertificate (`POST /iam/v1alpha1/`) - - CreateJWT (`POST /iam/v1alpha1/`) - - DeleteJWT (`DELETE /iam/v1alpha1/`) - - DeleteSaml (`DELETE /iam/v1alpha1/`) - - DeleteSamlCertificate (`DELETE /iam/v1alpha1/`) - - EnableOrganizationSaml (``) - - UpdateSaml (`PATCH /iam/v1alpha1/`) \ No newline at end of file