FHIR Chat · Sandbox Updates · cds hooks

Stream: cds hooks

Topic: Sandbox Updates


view this post on Zulip Kevin Shekleton (May 09 2018 at 13:19):

Hi everyone! I have some updates on the Sandbox that I wanted to bring everyone's attention to. This also important for those attending the Connectathon this weekend in Cologne!

First, the Sandbox that has served us well over the past three years has been retired and is now available at http://legacy-sandbox.cds-hooks.org. We will keep this Sandbox around indefinitely, both the deployment and the source code which now is available at https://github.com/cds-hooks/legacy-sandbox

Next, we have a new Sandbox that has been written for the ground up for CDS Hooks 1.0! This new Sandbox retains the same look & feel from the legacy Sandbox as well as supporting the CDS Hooks 1.0 specification. This Sandbox is what is deployed when you go to http://sandbox.cds-hooks.org (note that HTTP also works!). The source code for our Sandbox is available at https://github.com/cds-hooks/sandbox

Why the change?

The legacy Sandbox was originally written as a demo prototype by @Josh Mandel to illustrate the the idea of CDS Hooks. We got a ton of mileage out of this original codebase (thank you Josh!) but as we approached our 1.0 release, we realized that we needed to formalize and harden the codebase. The new Sandbox is built using the same technology (React JS app) but using the latest version and a design for (internal) testability in mind. That means our new Sandbox has a complete test suite so we have a lot more confidence in our changes. And finally, we split out the default CDS Services out into their own project to keep a nice separation of concerns between the Sandbox and those default CDS Service.

I want to thank @Zach Plata who has been working tirelessly on enhancements to the legacy Sandbox over the past year as well as writing our new Sandbox from the ground up!

view this post on Zulip Kevin Shekleton (May 09 2018 at 13:20):

While everything is live right now, note that we're still in the process of updating those default CDS Services -- those will be working here shortly.

view this post on Zulip Kevin Shekleton (May 09 2018 at 13:22):

As you all target your implementations for our proposed CDS Hooks 1.0 specification, please use the new Sandbox (again, available at http://sandbox.cds-hooks.org) and test your CDS Services there as it is up to date with our spec.

If you encounter any issues or have ideas for an enhancement, please don't hesitate to log a Github issue. We also would love your pull requests! :github:

view this post on Zulip Kevin Olbrich (May 09 2018 at 15:06):

@Kevin Shekleton have you tried launching the new cds-hooks sandbox from the HSPC sandbox? I keep getting a 'Error invalid_grant' page when I try to launch from there. (with Invalid redirect: http://sandbox.cds-hooks.org/ does not match one of the registered values: [http://localhost:8080/])

view this post on Zulip Kevin Shekleton (May 09 2018 at 16:11):

Oops, thanks! We're on it now...

view this post on Zulip Zach Plata (May 09 2018 at 16:12):

Hi @Kevin Olbrich , thanks for catching this! We have a SMART app registered to launch the Sandbox at localhost, and one at the sandbox.cds-hooks.org site; forgot to switch this. It should be fixed soon here.

view this post on Zulip Zach Plata (May 09 2018 at 17:32):

The fix has been deployed and the Sandbox should launch securely as expected now.

view this post on Zulip Kevin Olbrich (May 09 2018 at 18:11):

@Zach Plata I'm still getting this Invalid redirect: http://sandbox.cds-hooks.org/ does not match one of the registered values: [http://localhost:8080/]

view this post on Zulip Zach Plata (May 09 2018 at 18:15):

Hm..could you try clearing your cache? Also, are you using your own personal HSPC instance that came with the default CDS Hooks app?

view this post on Zulip Kevin Olbrich (May 09 2018 at 18:15):

@Zach Plata yes, it's my own sandbox with the cds-hooks app.

view this post on Zulip Kevin Olbrich (May 09 2018 at 18:17):

@Zach Plata ok, got it. Clearing the cache might have been all that was required.


Last updated: Apr 12 2022 at 19:14 UTC