Open
Conversation
… with content loader into the stack
DerDaehne
force-pushed
the
feature/remove-mailhog
branch
from
e2ba26f to
9c5498e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This MR will remove Mailhog fully from the gitops-playground.
Users will still be able to configure their own mailserver to be used with the gitops-playground platform via the provided config flag. Furthermore, if required, users can simply provision a small mailserver via the content loader feature.
An example for that is given within: "application-content-helm-mailpit-example.yaml"