`test.sh` is making incorrect assumptions

[franck-boullier]

The problems:

Incorrect AWS profile:

In the file test.sh
The code reads:

apienroll/test.sh

Line 3 in 6cfcb24

-H "Authorization: Bearer $(aws --profile uneet-dev ssm get-parameters --names API_ACCESS_TOKEN --with-decryption --query Parameters[0].Value --output text)" \

This IS WRONG: we should NOT use uneet-dev here but the correct value based on

• Installation ID (AWS parameter INSTALLATION_ID)
• Stage (AWS parameter STAGE)

The correct value for uneet-dev for a given environment is also declared in Travis Setting.
It is then passed on as the variable TRAVIS_PROFILE.

Problematic assumptions:

apienroll/test.sh

Line 7 in 6cfcb24

"userId": "32",

assumes that there is a user with userId = 32 in the installation <-- This might NOT be true.

apienroll/test.sh

Line 8 in 6cfcb24

"userApiKey": "kwmJ6OT6tzEdmctCrT3uEt7kMnLEqlzckW4eaTvX"

assumes that userApiKey for user 32 has a certain value in the installation <-- This might NOT be true.

[kaihendry]

RE ${INSTALLATION_ID}-${STAGE}, you have a chicken and egg problem as described upon #4 (comment)

I agree userId and userApiKey is bad, but since these couldn't be created programatically (I asked you several times about this), I have no choice but to hard code it. Yes it could go into a parameter store, but that doesn't really help. It only adds a level of indirection.