-
Notifications
You must be signed in to change notification settings - Fork 61
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
[Feature] Have a --dev parameter able to configure gitea and argocd with default: username/password #441
Comments
Remark: As argocd generates itself the:
then we cannot use our own password and a different strategy should be used in this case. The strategy could be:
|
For gitea we could pass the idpbuilder/pkg/controllers/localbuild/gitea.go Lines 94 to 105 in 2902af3
|
Signed-off-by: cmoulliard <[email protected]>
I think I'd rather name it more like kubectl. So something like |
|
…a new password. cnoe-io#441 Signed-off-by: cmoulliard <[email protected]>
… - developer. Create a kubeClient part of the k8s util package. cnoe-io#441 Signed-off-by: cmoulliard <[email protected]>
Signed-off-by: cmoulliard <[email protected]>
Signed-off-by: cmoulliard <[email protected]>
Signed-off-by: cmoulliard <[email protected]>
…veloper's password. cnoe-io#441 Signed-off-by: cmoulliard <[email protected]>
…noe-io#441 Signed-off-by: cmoulliard <[email protected]>
…noe-io#441 Signed-off-by: cmoulliard <[email protected]>
Have you searched for this feature request?
Problem Statement
Suggestion
Have a
--dev
parameter that we could use when we create a new cluster and able to configure gitea and argocd with default: username/passwordWhy ? It is really a pain when we develop locally new packages and we recreate cluster several times to have to re-log manually using the UI of gitea/argocd instead of storing in the browser's password store the username/password used for
dev
purposesPossible Solution
Change the existing code
Alternatives Considered
No response
The text was updated successfully, but these errors were encountered: