Skip to content
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

[???] Create custom keycloak image for testing #371

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

MartinFlores751
Copy link
Contributor

The environment should start the same on every standup by using the realm export. Asymmetric keys are only good for 10 years, I think. Remember to update before then!

Environment should be the same. Asymmetric keys are only good for
10 years I think. Remember to update before then!
@MartinFlores751
Copy link
Contributor Author

Rebuild image again for sanity check. Take out of draft if good.

@MartinFlores751 MartinFlores751 marked this pull request as ready for review November 15, 2024 18:59
@MartinFlores751
Copy link
Contributor Author

Builds good. Any future config changes should likely only see the example-realm-export.json change...

@MartinFlores751
Copy link
Contributor Author

I think we can use #242 for this.

@trel
Copy link
Member

trel commented Nov 15, 2024

242 feels good and right.

Copy link
Contributor

@korydraughn korydraughn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's include words about the asymmetric keys in the README too.

Include as much info that seems helpful to the developer as possible.

@@ -0,0 +1,18 @@
FROM quay.io/keycloak/keycloak:latest as builder
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add comments above the FROM lines which explain what the whole section is for. The comments will also serve as separators for the multi-stage build.

@@ -0,0 +1,18 @@
FROM quay.io/keycloak/keycloak:latest as builder

# Configure stuff
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please expand "stuff" into more words.

ENV KEYCLOAK_ADMIN=admin
ENV KEYCLOAK_ADMIN_PASSWORD=admin

# Optimized build thing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please expand on this. It's not clear what this means.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there other options of interests to add/document in the Dockerfile?

It's fine if the answer is no.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a few comments to the top of the file explaining what it's for on a high level.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a README to this directory which describes this component.

The top-level README for the repo can point to it where necessary.

Hmm, we should add a README to the /test directory in general. Then we don't need a README for each subdirectory under /test.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ha, oops, you said this...

@trel
Copy link
Member

trel commented Nov 15, 2024

can make a test/README.md to keep it scoped, if that seems a good idea.

Copy link

@alanking alanking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of minor comments. Solid Dockerfile

@@ -0,0 +1,16 @@
FROM quay.io/keycloak/keycloak:latest as builder

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to pin to a specific version to avoid incompatibility with a future release? Maybe latest is... good enough...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's pin it. Debugging becomes more difficult when everyone is using different versions of a thing.

Comment on lines +17 to +18
# Standard entrypoint
ENTRYPOINT ["/opt/keycloak/bin/kc.sh"]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is the ENTRYPOINT of the base image, we probably don't need to override it here. Doesn't hurt, though.

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.

4 participants