-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[minor] Added HMAC to COS role #1215
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ansible-devops role now allows the config scope to be set and the use_hmac to be set, which is all fine. But that means that for an env that has assist, mvi and manage installed we need the following set:
- objectstorage-cfg at system scope with use_hmac as false
- objectstorage-cfg at app/workspace(for manage) scope with use_hmac as true
I don't think the changes here allow the scope to be set or for more than one config/dependency to be created
I don't know how to handle this but the aim for the changes are to give new environment variable support for ansible-devops role. @chiragcsatani can you confirm what we need to do ? This is to fix fvt issue for manage but for assist & mvi we may have to revisit this code and ansible-devops role also. |
As a part of https://jsw.ibm.com/browse/MAXMF-455 we added new environment variable USE_HMAC to create COS with HMAC support. There is PR ibm-mas/ansible-devops#1407 in ansible-devops regarding this.