infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Spector (JIRA)" <>
Subject [jira] [Commented] (INFRA-18667) move emails from sent to 'dev@' send to 'issues@' instead
Date Tue, 02 Jul 2019 11:15:00 GMT


Brian Spector commented on INFRA-18667:

Hi [~dfoulks] we are still getting git generated emails into dev@ channel. As an example,
see below

This is an automated email from the ASF dual-hosted git repository.

kittohoward pushed a commit to branch dta/overview
in repository

commit e4b09f1b76b0cc2cf0c4434b6702172f886a9c03
Author: howardkitto <>
AuthorDate: Tue Jul 2 10:42:15 2019 +0100

    ecrypted envelope
 docs/api-details/   |  10 ++++++++++
 docs/dta-details/           |  22 ++++++++++++++++++++++
 website/static/img/dta/Envelope.png | Bin 0 -> 18988 bytes
 3 files changed, 32 insertions(+)

diff --git a/docs/api-details/ b/docs/api-details/
new file mode 100644
index 0000000..6f7b9f6
--- /dev/null
+++ b/docs/api-details/
@@ -0,0 +1,10 @@
+id: configuration
+title: Configuration
+sidebar_label: Configuration
+Config file
+Env vars
\ No newline at end of file
diff --git a/docs/dta-details/ b/docs/dta-details/
new file mode 100644
index 0000000..e0184f6
--- /dev/null
+++ b/docs/dta-details/
@@ -0,0 +1,22 @@
+id: usage
+title: Using Milagro DTA
+sidebar_label: Using Milagro DTA
+Milagro DTA is designed to be built into the workflow of any organisation that needs to entrust
another organisation to store the secret part of a key pair securely. It provides a [simple
REST api](/swagger/index.html) "out-of-the-box" that can easily be integrated with an existing
back office system or attached to a front-end application (or called from CURL, Postman, Swagger
etc. if you just want to see what it does).
+The API has three parts to it:
+1. _Identity Endpoints_ - that support creation and retrieval of identity documents
+2. Secret Endpoints
+    1. Creates orders for new secrets
+    2. Requets for existing secret keys to be revealed (redeemed)
+    3. Allows orders to be searched and listed
+3. Fulfilment RPC - these are the server-to-server calls that enable the Principal DTA to
communicate with the Fiduciary
+## Bootstrapping An Identity
+In order to run a Milagro DTA Node it needs to be configured with an idenity. This is usually
passed to the node via one of the [configuration options](api-details/, however
if you are running a server for the first time it will prompt you to create a new one.
diff --git a/website/static/img/dta/Envelope.png b/website/static/img/dta/Envelope.png
new file mode 100644
index 0000000..28f8ff4
Binary files /dev/null and b/website/static/img/dta/Envelope.png differ

> move emails from sent to 'dev@'  send to 'issues@' instead
> -------------------------------------------------------------------------
>                 Key: INFRA-18667
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Mailing Lists
>         Environment: Apache Milagro
>            Reporter: Brian Spector
>            Assignee: Drew Foulks
>            Priority: Critical
> We are finding the amount of email generated by sent to
overwhelming and hard to have conversations over the dev channel.
> We've had a new channel created. Can you please route all issues
created by git to 
> instead of currently going to dev@ 
> Also, any email coming from 
> "This is an automated email from the ASF dual-hosted git repository."
> If you could also route these emails into that would be much
> The list of repos this needs to happen on priority-wise are:
> Thanks
> Brian

This message was sent by Atlassian JIRA

View raw message