Skip to content

Conversation

@kptdobe
Copy link
Contributor

@kptdobe kptdobe commented Jan 12, 2026

As DA ops team, we need to be able to support customers with common ops tasks:

  • update their config (typical scenario: someone excluded themselves from CONFIG editing)
  • read / write their content (inspect their prod content)

Today, if they still can, we ask the customers to add an IMS org / our email address to their CONFIG to access their projects. Or we go directly to Cloudflare DA_CONFIG KV or R2 storage. This is a really cumbersome or error prone process.

This PR: transparently add one IMS org (configured via the DA_OPS_IMS_ORG env variable) to each customer config. Whoever is member of the IMS org get full access (config and content) to all projects via the UI. Much easier to debug and fix problems.
We only need to be careful with IMS org management.

@tripodsan tripodsan merged commit 8e35211 into main Jan 13, 2026
8 of 9 checks passed
@tripodsan tripodsan deleted the opsperm branch January 13, 2026 09:27
adobe-bot pushed a commit that referenced this pull request Jan 13, 2026
# [1.1.0](v1.0.5...v1.1.0) (2026-01-13)

### Bug Fixes

* no exception if no destination provided ([#231](#231)) ([df0939f](df0939f))

### Features

* add special IMS org with full access ([#233](#233)) ([8e35211](8e35211))
adobe-bot pushed a commit that referenced this pull request Jan 13, 2026
# [1.1.0](v1.0.5...v1.1.0) (2026-01-13)

### Bug Fixes

* no exception if no destination provided ([#231](#231)) ([df0939f](df0939f))
* repair release ([#234](#234)) ([104409e](104409e))

### Features

* add special IMS org with full access ([#233](#233)) ([8e35211](8e35211))
@adobe-bot
Copy link
Collaborator

🎉 This PR is included in version 1.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants