-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat(quickstart): Remove kafka-setup as a hard deployment requirement #7073
feat(quickstart): Remove kafka-setup as a hard deployment requirement #7073
Conversation
Note, this PR will fail if run locally to test the new flag because it assumes that the files already exist in Github. You will need the following git diff to test this locally:
|
docker/quickstart/docker-compose.consumers-without-neo4j.quickstart.yml
Outdated
Show resolved
Hide resolved
Like the approach, probably you've found an issue with the mce consumer quickstart generation. |
938b449
to
0255c94
Compare
0255c94
to
3b15857
Compare
docker/quickstart/docker-compose-without-neo4j-m1.quickstart.yml
Outdated
Show resolved
Hide resolved
docker/quickstart/docker-compose-without-neo4j-m1.quickstart.yml
Outdated
Show resolved
Hide resolved
docker/quickstart/docker-compose-without-neo4j-m1.quickstart.yml
Outdated
Show resolved
Hide resolved
I am wondering if we even need a separate m1 flavor anymore? Seems like folks have moved to generate arm images consistently, however perhaps I am overlooking something here. |
There are a few images that we need M1 alternatives for still such as Postgres & Neo4j. |
This PR does a few improvements to our docker cli behaviour, namely:
kafka-setup
job optional behind the flag:--kafka-setup
which works similar to standalone consumer containers.yq
Checklist