Use email api to setup nexus email capabilities #398
Merged
Conversation
This file contains 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
Using the official API will reduce code in this role. Furthermore, using an official API remove the need to deploy dedicated scripts. And such deploy can be annoying depending on the overall deployment (native, docker, docker-compose, kubernetes). So, using official API will offer the ability to reuse easier this role in much more context.
zeitounator
force-pushed
the
feature/use-email-api
branch
from
7083885
to
431c776
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use official API for setting email capabalities. This is a rework of #252 dropping support for too old nexus versions.
Replaces #252
Fixes #252