opendevstack
Add project specific cd user after for generating new components
Creation of new project with a project-specific-cd-user is a bit clumsy as prov-app doesn't communicate with Crowd or AD to create one in real time. For AD, I assume there can't be instant feedback and response to create a new technical user anyway. As a result of this lag, there can be a use case where project specific cd user is created after the project is already generated.
It would save developers time if this new user can then be added when generating new components. This would link the generated repo to that cd user as opposed to global cd user. @gerardcl @stitakis
Right now there can only be one "cd_user" per project (foo-cd namespace). Do you suggest to change that when generating a new component, or is your suggestion to have multiple "cd_user"s per project?
Sorry, a correction for above... I meant to say switching from global cd user to a project specific one, not adding a new one. So saving the developer time to change related resources:
- changing OC username/secret
- changing the user in project repo
- adding a new user to opendevstack quickstarters and jenkins shared lib repos
FYI
changing OC username/secret
that was - at the time - a conscious design decision. We intentionally kept the password out of ODS altogether, and we also avoided integrating ODS with the "user management process" (as that can differ a lot between companies). So unless we give that up, changing the secret manually is painful, but the most secure option right now.
Hm makes sense as a design decision. Then maybe we can add some documentation around which places need change in case someone need to change their cd user in the middle of the project. What do you think?