Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/859
+1 remains here. Solid work.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/859
+1
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/859
Nice. I'm glad you uncovered the issue with the REST API. Reaffirming +1
---
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/859
**Testing**
Run the EC2 deployment
```
cd metron-deployment/amazon-ec2
./run.sh
```
The dev profile should now be set for the REST API. This is the same way we
spin up
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/859
Just a heads up, I've added the spring profile to the ec2 blueprint.
---
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/859
Good catch @mmiklavc. Would be nice to get that added to the blueprint so
it just happens.
---
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/859
I just found another item when going through an AWS install. We don't setup
users for the REST API. From what I can tell, we do this via blueprint when we
install full-dev from a setting in
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/859
+1 Thanks!
---