Guang, I agree that this is primarily a user experience & discoverability issue. Having inconsistent API behaviors that depend on the contents of keystone.conf needs to be fixed.
1. Certainly breaks backwards compatibility in the API.
2. Violates API change guidelines.
3. Is a workaround that does nothing to improve the user experience. The API should be self-consistent.
Guang, I agree that this is primarily a user experience & discoverability issue. Having inconsistent API behaviors that depend on the contents of keystone.conf needs to be fixed.
1. Certainly breaks backwards compatibility in the API.
2. Violates API change guidelines.
3. Is a workaround that does nothing to improve the user experience. The API should be self-consistent.