Actions
Task #11595
closed
Duplicated tokens on SmartGears/container.xml
Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Category:
Application
Target version:
Start date:
Apr 10, 2018
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Development
Description
Every time I try to upgrade catalogue-ws-d-d4s container.xml contains two entry of each scope (the token is the same).
The launched command is:
./run.sh smartgears-node.yml -i inventory/hosts.dev -l 'catalogue_ws_dev' -e "gcube_admin_token=7c66c94c-7f6e-49cd-9a34-909cd3832f3e-98187548"
Updated by Andrea Dell'Amico about 7 years ago
- Status changed from New to In Progress
It's a known effect of the changes on the script that manages the scopes. Until I find the time to completely rewrite the script, you have some options:
- live with the duplicates
- Do not pass the token when running the playbook if you do not need to add any new scopes from the playbook variables themselves. This way, the scopes found into the smartgears state will be used
- Pass the token if you want add scopes from the playbook. If you do not need to merge additional scopes from the smartgears state, add an additional variable to your ansible command:
-e 'smartgears_merge_scopes=False'
Updated by Andrea Dell'Amico about 7 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Updated by
Actions
