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

[IMPROVEMENT] Naming scheme #22

Open
aborroy opened this issue Apr 5, 2022 · 1 comment
Open

[IMPROVEMENT] Naming scheme #22

aborroy opened this issue Apr 5, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@aborroy
Copy link
Contributor

aborroy commented Apr 5, 2022

Current naming scheme may be confusing:

keystores/
├── alfresco
│   ├── keystore
│   ├── ssl.keystore
│   └── ssl.truststore
├── client
│   └── browser.p12
├── solr
│   ├── ssl-repo-client.keystore
│   └── ssl-repo-client.truststore
└── zeppelin
    ├── ssl-repo-client.keystore
    └── ssl-repo-client.truststore

Improvement

Simplify naming to avoid confusions:

  • keystore >> metadata.keystore
  • ssl.keystore >> repo.keystore
  • ssl.truststore >> repo.truststore
  • ssl-repo-client.keystore >> solr.keystore
  • ssl-repo-client.truststore >> solr.truststore

Additionally internal alias naming may be revisited.

@aborroy aborroy added the enhancement New feature or request label Apr 5, 2022
@hi-ko
Copy link

hi-ko commented Apr 6, 2022

to add:

  • browser.p12 >> browser-repoclient.p12

to allow an admin to generate also p12 stores for the other parts without nameclashes.

.. or even better: to remove the need for a browser-client special case we could always generate a browser-*.p12 to be imported in a browser for any keystore we generate, so an admin can test/debug any part, not just as a from solr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants