docs(s3): clarify AWS CLI v2.23+ workaround + restructure lifecycle/d…#308
Closed
aelttil wants to merge 779 commits into
Closed
docs(s3): clarify AWS CLI v2.23+ workaround + restructure lifecycle/d…#308aelttil wants to merge 779 commits into
aelttil wants to merge 779 commits into
Conversation
Mise à jour de la doc des métriques VM IaaS, conso kwh & graph tooltip
…cumentation Provider Terraform - Ajout de la documentation
Correction usingharbor
Add files for marketplace newsletter
…s-btu Add files for marketplace newsletter
OpenIaaS - Ajout de la partie Sauvegarde
…entation-support 198 mise a jour de la documentation support et traduction de usingharbor
…name-from-the-official-documentation 223 delete shiva technical name from the official documentation
This reverts commit 6129ecf.
Slu 20251206
Kub managé - Ajout OpenCost et retrait de KubeCost
…ross all languages
….) to fix docusaurus build
…vm_instances/... syntax) to resolve 404 on GH pages
…e packages Fixes CVEs detected by Harbor/Trivy on image 3.24.3: - libcrypto3/libssl3 (3.3.3-r0 -> 3.3.7-r0) - libxml2 (2.13.4-r3 -> 2.13.9-r0) - libxslt, libexpat, libpng, zlib, c-ares, musl, xz-libs, busybox, curl Applied to Dockerfile and Dockerfile.prebuilt (nginx:stable-alpine stage).
…AJ changelog et memory bank - Fix ContentSplitter : ne coupe plus au milieu des blocs de code - Nouvelles methodes : _find_code_block_ranges, _is_inside_code_block, _find_safe_split_point - Migration modele traduction : qwen3-2507:30b-a3b vers qwen3.6:35b (contexte 250k) - Changelog : ajout 3 entrees manquantes (stockage IOPS, sauvegarde IaaS, DB sizing) - Memory Bank : mise a jour complete (nouveaux services, etat couverture 97%)
…ranslation hashes
Migration complète des chemins d'images et nettoyage du système de traduction :
Images (208 fichiers migrés) :
- ./images/ → @site/docs/.../images/ (165 fichiers FR + i18n)
- ../images/ → @site/docs/.../images/ (43 fichiers FR + i18n)
- Fix cross-dir ../console/images/ dans iaas_vmware/quickstart.md
- Suppression de 11 dossiers images orphelins dans i18n/
Traductions & hash :
- Resync translation-meta.json (157/157 fichiers synchronisés)
- extract_changelog.py : ajout mise à jour automatique des hash
- Suppression de oldies/translate.js (script legacy)
- scripts/README.md : suppression section legacy, ajout extract_changelog
Fixes MDX :
- batch.md : échappement {batch_id} et {file_id} (FR + 4 langues)
- contact_partner.md EN : import manquant marketplaceContactEmail
- usinggpu.md IT : typo nvidasmi → nvidiasmi
Documentation :
- README.md : section traduction enrichie, règle images @site/docs
- changelog_produits.md : tronqué avant v4.0 (~2600 → ~420 lignes)
- memory-bank/documentationStatus.md : état mis à jour
Build : ✅ SUCCESS (toutes les langues)
Managed Kubernetes / Managed Core Kubernetes SLA is 99.95% Changed storage pre-requisites for Managed Kubernetes / Managed Core Kubernetes
The file was committed before the .gitignore rule existed (or before a previous git rm --cached). The rule on line 19 of .gitignore had no effect on the already-tracked file. Removing it from the index keeps the local copy intact but stops future modifications from being committed. NOTE: any API key that was previously committed to history must still be considered compromised and rotated separately on the LLMaaS side. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- README.md: collapse the duplicated Translation System section to a short pitch + one critical warning (never edit i18n/ manually) + a link to scripts/README.md (single source of truth). - scripts/README.md: add a Python venv step in the Installation section to avoid polluting the system Python, and a new "Règles importantes" block grouping the warnings previously duplicated in the main README (i18n manual edits, absolute @site/docs image paths, .notranslation). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… SLA - Intervalle minimum de réplication passé de 1 minute à 15 minutes - Ajout d'un avertissement expliquant que le RPO est un objectif best effort - Le RPO effectif dépend du taux de changement (change rate) des données - Aucun SLA contractuel n'est associé au RPO
…es/it - changelog.md: resync with FR source (debt from recent dev commits) - iaas_opensource/concepts.md: translate RPO 15 min change from fix(openiaas) commit on this branch - translation-meta.json: update SHA-256 hashes accordingly Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…config The README and .env.example previously duplicated the env vars list, which had silently drifted from config.py defaults: - TRANSLATION_MODEL was still qwen3:30b-a3b (obsolete, causes HTTP 404) - CONCURRENT_TRANSLATIONS doc said 8 but real default is 4 - MAX_TOKENS_PER_BLOCK doc said 5000 but real default is 4000 - MODEL_TYPE / MAX_MODEL_CONTEXT_LENGTH / BUFFER_TOKENS were undocumented scripts/translate_py/.env.example: - Rewritten as self-documenting with inline comments (role, default, valid range) for every variable supported by config.py - TRANSLATION_MODEL updated to qwen3.6:27b (current default) - Added MODEL_TYPE, MAX_MODEL_CONTEXT_LENGTH, BUFFER_TOKENS - Documented TRANSLATION_LOCAL_MODE and DOC_BASE_PATH scripts/README.md: - Removed the duplicated env vars block - Points to .env.example as the single source of truth - Adds a note explaining why duplication was removed Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…o-15min fix(openiaas): RPO réplication minimum 15 min + avertissement absence…
…eletion concepts
- quickstart.md: rewrite the AWS CLI section to explicitly mention the
v2.23.0+ default CRC64NVME issue on ECS-based storage. Sets both
request_checksum_calculation AND response_checksum_validation to
when_required (the latter was missing — downloads can also fail
without it). Restores the endpoint explanation that was removed.
- concepts.md: introduce "Gestion du cycle de vie et protection des
données" section that clearly separates two often-confused mechanisms:
* lifecycle policy → actively deletes objects after N days
* deletion protection → passively prevents deletion for N days
Adds a note explaining the difference with standard S3 Object Lock
(Cloud Temple's mechanism is bucket-level, doesn't require versioning).
- quickstart.md: move detailed concept explanations to concepts.md
(the quickstart stays action-focused) and link between the two pages.
Supersedes #304. Empirically tested on a CT S3 bucket:
- XAmzContentSHA256Mismatch reproduced without the fix
- both request_checksum_calculation and response_checksum_validation
validated end-to-end (upload + download)
Co-Authored-By: bquinsac <119865939+bquinsac@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…eality
Following review feedback on the previous draft of the lifecycle vs.
deletion protection section:
- Lifecycle: drop the inaccurate claim that ECS automatically deletes
expired objects. The Lifecycle Delete Scanner (LDS) is disabled by
default on ECS 3.2.1+, so actual deletion depends on platform-side
configuration. Adds an :::info note pointing users to support if
expiration doesn't take effect.
- Deletion protection: clarify that activation is NOT self-service —
it requires an explicit support request, and is contractually binding.
- Adds a :::danger block on irreversibility with explicit business
consequences:
* the configured duration cannot be shortened, even by Cloud Temple
* if a 99-year protection is set, the data is locked for 99 years
* if the customer stops using the service or terminates the contract,
the locked volume remains billable pro-rata until the period ends
* no bypass mechanism exists (shared SecNumCloud infrastructure)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…eletion concepts
quickstart.md: rewrite the AWS CLI section to explicitly mention the v2.23.0+ default CRC64NVME issue on ECS-based storage. Sets both request_checksum_calculation AND response_checksum_validation to when_required (the latter was missing — downloads can also fail without it). Restores the endpoint explanation that was removed.
concepts.md: introduce "Gestion du cycle de vie et protection des données" section that clearly separates two often-confused mechanisms:
quickstart.md: move detailed concept explanations to concepts.md (the quickstart stays action-focused) and link between the two pages.
Supersedes #304. Empirically tested on a CT S3 bucket: