You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "George Reyes (JIRA)" <ji...@apache.org> on 2015/01/30 00:13:34 UTC

[jira] [Commented] (USERGRID-371) Ensure that all services that use amazon keys are using the same identifier for those amazon keys.

    [ https://issues.apache.org/jira/browse/USERGRID-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297877#comment-14297877 ] 

George Reyes commented on USERGRID-371:
---------------------------------------

This would require changing the json that the import/export process currently uses to use the following identifier

    public static final String ACCESS_KEY_ENV_VAR = "AWS_ACCESS_KEY_ID";

This all caps letter would look weird in the existing json structure. 

> Ensure that all services that use amazon keys are using the same identifier for those amazon keys.
> --------------------------------------------------------------------------------------------------
>
>                 Key: USERGRID-371
>                 URL: https://issues.apache.org/jira/browse/USERGRID-371
>             Project: Usergrid
>          Issue Type: Technical task
>          Components: Stack
>            Reporter: George Reyes
>            Assignee: George Reyes
>
> Currently the way notifications looks for access and secret keys is different from the way that export and import services look for keys. This needs to be changed so that we all look for the same name of the keys.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)