Skip to content

Conversation

@longshuicy
Copy link
Member

@longshuicy longshuicy commented Mar 23, 2023

I updated the readme:

After modifying backend API, update autogenerated client function calls:
   - Backend must be running: `docker-compose -f docker-compose.test.yml up`
   - Run codege: `npm run codegen:v2:test`
   

For some reason the built backend in docker container generate a very minor difference than the one we use in pycharm
image

Might be related to keycloak?

@longshuicy longshuicy changed the title WIP 379 GitHub action to run codegen automatically when there is backend change 379 GitHub action to run codegen automatically when there is backend change Mar 24, 2023
@longshuicy longshuicy marked this pull request as ready for review March 24, 2023 20:31
@longshuicy longshuicy requested a review from tcnichol March 24, 2023 20:32
@lmarini
Copy link
Member

lmarini commented Mar 28, 2023

That endpoint /broker/{identity_provider}/token proxies the return of a keycloak call. All our docker file seem to fix the keycloak version to 19.0, but maybe somehow we are running a different version in one case.

@longshuicy
Copy link
Member Author

@lmarini i commented out the get_idenity_provider_token and it seems to be consistent now. I reverted the README instruction on how to run codegen. Let me know what else is left on this PR? Thanks~

@lmarini lmarini merged commit ce52bdf into main Apr 6, 2023
@lmarini lmarini deleted the 379-github-action-to-run-codegen-automatically-when-there-is-backend-change branch April 6, 2023 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Github action to run codegen automatically when there is backend change

3 participants