6 results found

1. API support for environment copy-back lifecycle and post-copy script execution

   As a development team managing multiple lower environments, we want API/PowerShell endpoints to orchestrate the full copy-back workflow, including a mechanism to run registered post-copy maintenance scripts, so that I can automate environment refresh end-to-end without manual PaaS Portal interaction.

   Currently, the copy-back workflow requires manual steps in the PaaS Portal (stop environment, copy databases/blobs from Production, start environment). After the copy, teams must anonymise PII from the copied databases to comply with GDPR before the environment can be used. This anonymisation step cannot be triggered or orchestrated through the platform.

   We would like the EpiCloud module or REST API to expose:

   1. Stop/start an environment without triggering a code deployment
   2. Copy database and blobs from one environment to another
   3. A webhook or callback when the copy operation completes (so we know when to start the anonymisation or "post-copy scripts")
   4. The ability to register and execute approved SQL scripts as a post-copy step (e.g. PII anonymisation, index rebuilds, configuration updates for non-production)
   5. A completion report confirming which scripts ran successfully, for GDPR compliance audit evidence

   Option 4 could take the form of a "post-copy scripts" folder in the project repository that the platform executes automatically after a copy completes, or a managed script execution endpoint that accepts pre-registered/approved scripts.

   This would allow teams to build compliant, scheduled, hands-off environment refresh pipelines without needing direct database access, which most hosted customers do not have.

   As a development team managing multiple lower environments, we want API/PowerShell endpoints to orchestrate the full copy-back workflow, including a mechanism to run registered post-copy maintenance scripts, so that I can automate environment refresh end-to-end without manual PaaS Portal interaction.

   Currently, the copy-back workflow requires manual steps in the PaaS Portal (stop environment, copy databases/blobs from Production, start environment). After the copy, teams must anonymise PII from the copied databases to comply with GDPR before the environment can be used. This anonymisation step cannot be triggered or orchestrated through the platform.

   We would like the EpiCloud module or REST API… more

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Official guidance for HTTP QUERY method support in Optimizely DXP

   Summary

   The HTTP QUERY method (RFC 10008) provides a standardized way to perform safe, idempotent query operations while allowing a request body, addressing a long-standing limitation of GET.

   https://www.rfc-editor.org/info/rfc10008/

   https://tykok.medium.com/the-new-http-method-query-d1dc3efc35c4

   While ASP.NET Core applications can implement support for QUERY, developers deploying to Optimizely DXP also depend on the surrounding platform and infrastructure.

   Request

   Could Optimizely publish official guidance regarding support for the HTTP QUERY method in DXP?

   Specifically, it would be helpful to clarify:

   • Is QUERY currently supported throughout the DXP infrastructure?
   • If not, which components prevent support (Cloudflare, WAF, load balancers, Azure App Service, proxies, etc.)?
   • Are there any security considerations specific to QUERY that developers should be aware of?
   • Will QUERY be treated similarly to GET regarding safe/idempotent semantics where applicable?
   • Is support on the product roadmap, or is it considered out of scope?
   • If there is no current support, what is the recommended approach for developers who would otherwise benefit from QUERY?

   Why this matters

   Many APIs expose complex search and filtering operations that naturally fit a safe, idempotent request but exceed the practical limitations of GET query strings.

   The QUERY method provides a standards-based solution to this problem. As more frameworks begin supporting it, developers will naturally want to know whether Optimizely DXP fully supports the method before adopting it.

   Even if official support is not yet planned, having clear documentation describing the current state and any platform limitations would help developers make informed architectural decisions.

   Thank you for considering publishing official guidance.

   Summary

   The HTTP QUERY method (RFC 10008) provides a standardized way to perform safe, idempotent query operations while allowing a request body, addressing a long-standing limitation of GET.

   https://www.rfc-editor.org/info/rfc10008/

   https://tykok.medium.com/the-new-http-method-query-d1dc3efc35c4

   While ASP.NET Core applications can implement support for QUERY, developers deploying to Optimizely DXP also depend on the surrounding platform and infrastructure.

   Request

   Could Optimizely publish official guidance regarding support for the HTTP QUERY method in DXP?

   Specifically, it would be helpful to clarify:

   • Is QUERY currently supported throughout the DXP infrastructure?
   • If not, which components prevent support (Cloudflare, WAF, load balancers, Azure App Service, proxies, etc.)?
   • Are there any… more
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. DXP support for apex domain

   Currently DXP only supports complete hostnames containing both the subdomain and apex domain e.g. www.mywebsite.com.

   We would like to request support for configuring the apex (root) domain (e.g. mywebsite.com) as the primary domain within DXP.

   Traffic can then be redirected from www.mywebsite.com to mywebsite.com.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. IP Address restriction in Cloudflare

   It would be great if we could configure an IP Address whitelist in Cloudflare so that we only allow a specific set of source IP Addresses to be allowed to access our DXP instances. This will allow us to block public access to non-production environments

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Assess binding settings to resolve resets

   We need to evaluate whether setting the suggested Microsoft setting is worthwhile to resolve resets. As part of that effort, we would have to evaluate the risks of doing so.

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Identify and Aid Customers with Production Live-Locks

   There's the concept of a "dead" lock and a "live" lock. A live-lock is essentially a race condition within a production environment. It causes stair stepping of CPU usually until the server crashes.

   This often happens when a developer accidentally uses a non-thread safe object in a multi-threaded manner.

   The object (for example a HashSet) being used needs to be identified and a thread safe type needs to be replaced so that the live-lock goes away and the CPU goes back to normal.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating