You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the Import feature to import a revised configuration.
The import claims it is successful.
When I review the parameters I see that nothing has changed.
Note:
the comparison feature does work.
updating field and persisting them also works correctly
To Reproduce
Steps to reproduce the behavior:
${TEST_ADMIN_ENDPOINT} - the url for the Admin App Endpoint in TEST ${DEV_ADMIN_ENDPOINT} - the url for the Admin App Endpoint in DEV
This bug is actually in the ols-util code, and I believe it was fixed for geocoder last year, perhaps by this commit: bcgov/ols-util@c512342
We haven't tested/delivered a new version of router since then, so the new version of ols-util has not been included in the router yet. You could make this change in the POM but it will require testing as there are other changes to the ols-util that have not been tested in the router.
Describe the bug
I used the Import feature to import a revised configuration.
The import claims it is successful.
When I review the parameters I see that nothing has changed.
Note:
To Reproduce
Steps to reproduce the behavior:
${TEST_ADMIN_ENDPOINT}
- the url for the Admin App Endpoint in TEST${DEV_ADMIN_ENDPOINT}
- the url for the Admin App Endpoint in DEVI change the
dataSource.baseFileUrl
to something like 'this is a test'Response:
Additional Context:
pom.propertes
:The text was updated successfully, but these errors were encountered: