Support Tahoe 2.0 site configuration client#63
Conversation
4a80014 to
bc1ce1c
Compare
7030a72 to
8532952
Compare
d8f4471 to
231d7f7
Compare
e228c23 to
74dc07d
Compare
- fix author_view when wharf_url is missing - support rendering templates in tests - new author_view for studio - refactored tests - Tahoe Hawthorn is no longer supported in v4.0.0 due to the lack of Site Configuration Client. It will act as if it's installed on a Vanilla Hawthorn. - Install `tahoe-sites` and `site-configuration-client` to simulate Tahoe environment. - Add support for Tahoe 2.0 site by reading `LAUNCHCONTAINER_WHARF_URL` from Site Config Service `secret`s. Tahoe 1.0 sites will still use `site_values` as usual - Breaking change: Drop support for pre-Juniper Tahoe installations. The last version to support Hawthorn is `3.0.0` need to complicate the XBlock with caching calls. - Simplify reading the Wharf URL * Read from `ENV_TOKENS` for regular Open edX installation (non-Tahoe) * Read from [Site Configuration Client](https://github.com/appsembler/site-configuration-client/) for Juniper+ installations - Refactored unit tests - Refactor testing environments in `tox.ini` to test for `tahoe` and non `tahoe` environments removing `tox-gh-actions`. - Remove complex and low-value caching for `wharf_url`
74dc07d to
7133ab2
Compare
briandant
left a comment
There was a problem hiding this comment.
many thanks, @OmarIthawi!
| - Install `tahoe-sites` and `site-configuration-client` to simulate Tahoe environment. | ||
| - Add support for Tahoe 2.0 site by reading `LAUNCHCONTAINER_WHARF_URL` from Site Config Service `secret`s. Tahoe 1.0 sites will still use `site_values` as usual | ||
| - Breaking change: Drop support for pre-Juniper Tahoe installations. The last version to support Hawthorn is `3.0.0` | ||
| need to complicate the XBlock with caching calls. |
There was a problem hiding this comment.
| need to complicate the XBlock with caching calls. | |
| - Do not complicate the XBlock with caching calls. |
There was a problem hiding this comment.
actually I think you can delete this line—it's duplicated below
|
|
||
| - Install `tahoe-sites` and `site-configuration-client` to simulate Tahoe environment. | ||
| - Add support for Tahoe 2.0 site by reading `LAUNCHCONTAINER_WHARF_URL` from Site Config Service `secret`s. Tahoe 1.0 sites will still use `site_values` as usual | ||
| - Breaking change: Drop support for pre-Juniper Tahoe installations. The last version to support Hawthorn is `3.0.0` |
There was a problem hiding this comment.
| - Breaking change: Drop support for pre-Juniper Tahoe installations. The last version to support Hawthorn is `3.0.0` | |
| - Breaking change: Drop support for pre-Juniper Tahoe installations. The last version to support Hawthorn is `3.0.0` |
|
|
||
| return url | ||
| def get_wharf_delete_url(self, required=True): | ||
| wharf_url = self.get_wharf_url(required=required) |
There was a problem hiding this comment.
I'm not sure I totally understand why we check for a wharf url and then return None. I think it's because we want this method (get_wharf_delete_url) to also make it clear that no URL is available. I'm also not sure why we'd return a delete URL if required=False but there is no wharf_url. I just need a docstring or comment here, I think.
| <div id="launcher_notification" class="hide"></div> | ||
| {% if enable_container_resetting %}<button type="button" class="ui-priority-primary" id="launcher_reset">Reset lab</button>{% endif %} | ||
|
|
||
| {% else %} |
| {% else %} | ||
| {# This message is intended to appear Studio for course authors. #} | ||
| <p><strong>Error: Unable to connect to the Appsembler Virtual Labs API endpoint.</strong></p> | ||
| <p>Please configure your Appsembler Virtual Labs API endpoint before using this XBlock.</p> |
There was a problem hiding this comment.
| <p>Please configure your Appsembler Virtual Labs API endpoint before using this XBlock.</p> | |
| <p>Please contact <a href="mailto:support@appsembler.com" target="_blank">Appsembler Support</a> so we can configure your Appsembler Virtual Labs API endpoint.</p> |
I could be wrong, but I don't think that the customer can configure this on his own, right? My suggested phrasing above captures that. If he can, I think we should talk with Matthew about writing some customer docs on that (or maybe the docs already exist).
|
Thanks Brian!! I'll follow up on all additions in another PR to avoid GitHub invalidating your review. |
clean up and review comments for PR #63
Fix RED-3385. Read Tahoe 2 site from
secreton Tahoe 2.0 sites and fromsite_valueson Tahoe 1.0 sites.Breaking change
Tahoe Hawthorn is no longer supported in v4.0.0 due to the lack of Site Configuration Client. It will act as if it's installed on a Vanilla Hawthorn.
TODO
ENV_TOKENSvalueENV_TOKENSvalue