Skip to content
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

Rename seed-default and seed-secrets #99

Closed
cdlliuy opened this issue Mar 12, 2020 · 1 comment
Closed

Rename seed-default and seed-secrets #99

cdlliuy opened this issue Mar 12, 2020 · 1 comment

Comments

@cdlliuy
Copy link
Contributor

cdlliuy commented Mar 12, 2020

Per discussion in #91, I created a new issue to bring this up

===================

@pdettor I just curious, are the names seed-secret and seed-defaults configurable? If we put them into the end-user's namespace where the service/bind resource being created, I would like to use a more explicitly name , i.e. secret-ibm-cloud-operator and config-ibm-cloud-operator to avoid the deletion by end-user.

Answered by @vazirim
@cdlliuy Sure, we can rename.

===================

@vazirim
Copy link
Member

vazirim commented Mar 12, 2020

This item is already part of #91

@vazirim vazirim closed this as completed Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants