-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update assets with new default config #809
Conversation
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
You need to run |
|
doing |
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
@LukasHirt @IljaN I updated the makefile to include the necessary yarn magic. It will execute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👯
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs |
@@ -84,12 +86,21 @@ lint: | |||
generate: assets | |||
go generate $(GENERATE) | |||
|
|||
.PHONY: assets | |||
assets: | |||
# TODO find a docker container with go and yarn so we can properly build assets in ci |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might make sense to introduce package caching as well (pre-fetched and bundled in CI container)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes ... but if I ask @micbar about that again he might want to hurt me ... we should schedule it for the next sprint ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need a dedicated container. Just split it in two commands. Run yarn build
in the nodejs container and go generate in the golang container. That is how we do it in all the other extensions.
Currently, I have to give consent after login because the generated
identifier-registration.yaml
lacks thetrusted: yes
config option.I regenerated the assets with
make clean generate build
but now I no longer have any web ui.Instead I now have this in the log:
Where is the make target to update the assets with the nice new branding @LukasHirt ?
I also made the
config/identifier-registration.yaml
just point to the../assets
so we don't forget to update the config in two places next time.