f24f5d4304
## Description > TL;DR Complimentary changes utlising `APPSMITH_CLOUD_SERVICES_SIGNATURE_BASE_URL` when mocking flagsmith on cloud services fetching the remote flags from cloud server, the the cacheableHelper function retrieves base url for cloud services. when running CI tests this base url is set to ted rather than the cloud services. In order to get the docker hosted CS url which is provided by this varialbe: `APPSMITH_CLOUD_SERVICES_SIGNATURE_BASE_URL` , we have to use another method `getBaseUrlWithSignatureVerification` to get the docker hosted CS url instead of `getBaseUrl` which gives TED url #### PR fixes following issue(s) Fixes #25787 #### Type of change - Chore: this may break EE sync > > > ## Testing > #### How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration. > Delete anything that is not relevant - [ ] Manual - [ ] JUnit - [ ] Jest - [ ] Cypress > > #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| config-test.json | ||
| config.json | ||
| config.yml | ||
| labeler.yml | ||
| pull_request_template.md | ||
| release-drafter-template.yml | ||
| reviewers.yml | ||
| semantic.yml | ||