Clarify OPCP IAM default role impossible change#364
Conversation
Develop > Master alignment
Develop > Master alignment
Compare Develop base Master => Develop to master alignment
Develop > Master alignment
Develop > Master deployment
Develop > Master deployment
Develop > Master alignment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master alignment
* docs(port): apply legacy PR #9391 Available connectors for Kafka Connect Adds a new reference guide on OVHcloud Managed Kafka Connect. Hand-ported (EN + FR) under public-cloud/databases/kafkaconnect-available-connectors. Original-URL: ovh/docs#9391 * fix(docs): update weblinks * docs: proofread #9391 Kafka Connect connectors and symlink all locales to EN - EN: enrich SEO description, canonical Professional Services link phrasing, bump lastUpdated - Symlink fr/de/es/it/pl/pt → en (guide English-only across all 7 locales, no translation planned) * docs: restore French title on FR Kafka Connect connectors guide FR is a real file (English body) with a French title + (EN) marker so French readers see a localised title, instead of symlinking to en. * docs: refresh external connector doc links to canonical URLs Replace 15 redirecting links in the Kafka Connect connectors guide with their current canonical targets, so links no longer rely on redirects: - GitHub repo renames: aiven/* → Aiven-Open/* (http, jdbc, opensearch connectors) - Confluent docs moved to /kafka-connectors/{elasticsearch,s3-sink}/current/ - MongoDB docs.mongodb.com → www.mongodb.com/docs - Snowflake docs.snowflake.net → docs.snowflake.com - Lenses.io connectors moved to /latest/connectors/kafka-connectors/{sinks,sources}/ Applied to en + fr (de/es/it/pl/pt inherit via symlink). * fixes * fix(billing): use bare community.ovhcloud.com link without locale suffix * docs(public-cloud): bump lastUpdated on kafkaconnect-available-connectors * chore(release): update changelog 2026.06.02 [skip ci] * chore(release): update changelog 2026.06.02 [skip ci] * fix(data-platform): restore clickable image links on Data Platform landing guide (#111) The legacy guide made each landing card a link via an absolutely-positioned overlay anchor defined in an inline <style> block. That block was dropped during migration, so the cards rendered as empty zero-size anchors and the bare images only triggered medium-zoom. Rewrite the four cards as real <a> anchors (whole card is the link) with inline styles and theme-aware colors. Add a `mediumZoom` selector option so images tagged `className="no-zoom"` opt out of zoom and follow the link on click instead. The option is additive and affects no existing images. * chore(release): update changelog 2026.06.02 [skip ci] * Adding KMS & Secret Manager to HDS & ISO27K lists (#90) * Adding KMS & Secret Manager to HDS & ISO27K lists * date update * docs: add KMS and Secret Manager to HDS/ISO27k certification tables, collapse locales to symlinks --------- Co-authored-by: Benoit Chuchla <benoit.chuchla@ovhcloud.com> * docs(port): add OPCP Landing Zone Manager guide, align CloudStore terminology (#99) * docs(port): add OPCP Landing Zone Manager guide, align CloudStore terminology Port of legacy PR #9339 (OPCP - Landing Zone Manager). - New guide: landing-zone-manager-create-user-account (EN+FR real, 5 locales symlinked to EN) - CloudStore: rename "end users" to "Landing Zone Manager users" + add an L3-layer callout - Convert 5 untranslated CloudStore EN-copies to symlinks for cross-locale consistency - Add a "Landing Zone Manager" category to the OPCP sidebar Original-URL: ovh/docs#9339 Original-author: @VincentCasse * docs(opcp): proofread Landing Zone Manager guide and normalize community links - Restore NBSP before colons in the FR guide (lost during the legacy port) - Fix duplicated step heading: Step 3 is now "Share the first-login credentials" - Resolve first-login modality conflict: password change is now stated as mandatory - Use bare https://community.ovhcloud.com/ on all files (drop localized/legacy URL forms) - Minor EN rewording, and bump lastUpdated to 2026-06-02 --------- Co-authored-by: Benoit Chuchla <benoit.chuchla@ovhcloud.com> * chore(release): update changelog 2026.06.02 [skip ci] * fix(links): resolve community to bare community.ovhcloud.com for all locales (#114) Drop the /community/{locale} suffix so /links/community matches the bare URL used in guides. * docs(port): restore missing OVHcloud CLI tabs on additional-disk guide (#113) * docs(port): restore missing OVHcloud CLI tabs on additional-disk guide The "Via the OVHcloud CLI" tab was missing from both the attach and detach tab groups across all 7 locales. Legacy PR #9333 (2026-05-04) added it, but the 2026-05-28 port only reconciled PR #9356, so the CLI tabs were never carried over. Restores the storage-block create/attach/detach commands and their option/parameter tables, using the existing legacy translations per locale. lastUpdated bumped to 2026-06-02. Original-URL: ovh/docs#9333 * docs(port): fix CLI command syntax storage-block -> storage block Per PR review: the OVHcloud CLI command group is "storage block" (two words), not "storage-block". Applied to create/attach/detach across all 7 locales. * chore(release): update changelog 2026.06.02 [skip ci] --------- Co-authored-by: bs-ovh <63296875+bs-ovh@users.noreply.github.com> Co-authored-by: Benoit Chuchla <benoit.chuchla@ovhcloud.com> Co-authored-by: jessica <jskajunior41@gmail.com> Co-authored-by: gbarideau <130669353+gbarideau@users.noreply.github.com> Co-authored-by: benchbzh <73875792+benchbzh@users.noreply.github.com>
Develop > Master Deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment PR
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master
* fix(theme): enable responsive table wrapping (#209) * fix(theme): enable responsive table wrapping * fix(theme): drop unused .nowrap table opt-out * chore(scripts): update changelog commit message format * chore(release): update changelog 2026.06.16.2 * docs: add access-websites-view guide (de-revamped, classic Multisite references) (#216) * Publish Valkey 8.1 and 9.1 (#214) * Publish Valkey 8.1 and 9.1 * docs: date update --------- Co-authored-by: Fabien Bagard <fabien.bagard@ovhcloud.com> Co-authored-by: Benoit Chuchla <benoit.chuchla@ovhcloud.com> --------- Co-authored-by: bs-ovh <63296875+bs-ovh@users.noreply.github.com> Co-authored-by: Hassen <hassen.ben-fredj.ext@ovhcloud.com> Co-authored-by: Yoann Cosse <63302382+Y0Coss@users.noreply.github.com> Co-authored-by: Kazarus <78911684+Kazarus4@users.noreply.github.com> Co-authored-by: Meuh-42 <60978232+Meuh-42@users.noreply.github.com> Co-authored-by: Fabien Bagard <fabien.bagard@ovhcloud.com>
Develop > Master
Develop > Master
Develop > Master
Develop > Master deployment
Develop > Master deployment
Develop > Master
Develop > Master
Develop > Master
Develop > Master
Develop > Master deployment
Develop > Master
Develop > Master
Develop > Master deployment
Develop > Master deployment
Develop > Master deployment
Develop > Master
Develop > Master deployment
Y0Coss
left a comment
There was a problem hiding this comment.
Your branch contains one real commit touching the EN + FR of opcp/iam-rights-management.mdx.
The issue is that the branch has accumulated 46 commits, of which 45 are Merge pull request #NN from ovh/develop. Those are the result of merging develop into the feature branch repeatedly over a long time (from #54 all the way to #353), so the PR is hard to read for what is a small clarification.
Recommendation: rebase down to the single real commit
Since only one commit is yours, the cleanest fix is:
git fetch origin
git checkout fix/opcp-iam-default-role-warning
git reset --hard origin/develop
git cherry-pick 2acb2d41 # your "clarify default IAM role" commit
git push --force-with-lease
That leaves the PR at 1 commit / 2 files. Use --force-with-lease (not plain --force) so you don't clobber anything unexpected on the remote.
(Alternatively, just branch fresh off current develop, re-apply the two-file change, and open a new PR — sometimes quicker than untangling a stale branch.)
Going forward
To keep a branch in sync with the base, use git rebase origin/develop rather than git merge develop. Merging the base branch in is exactly what produces this pile-up of merge commits.
Heads-up: the force-push will drop review-comment anchoring on the old commits, but that's harmless here given the size of the change.
To handle a customer request/question to change the default role in OPCP from keycloak