Comment 5 for bug 1620999
Revision history for this message
| Nikhil Komawar (nikhil-komawar) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
A partial (temporary) fix for identity v3 (original issue reported scenario) is at https:/
I think that workaround makes sense as reverting the patch will break other team:
I was told that the initial request for defaults was from ansible team. So, if we remove them in a hurry it will destabilize given they must have had a setup accordingly.
However, I'm of opinion that the defaults values need to be something that all project can live with. So, we need to have some cross project convo with keystone (for what happens when *_id and *_name values clash -- best way to resolve), ansible and tempest v3 gate.
If possible, let's avoid defaults in the code and use them in the config file. That way given multiple accounts are allowed to be setup in the config file, individual teams are free to setup their account specific defaults in the file.