[GitHub] [solr-operator] janhoy commented on issue #85: Support uploading configsets through the operator

[GitBox <gi...@apache.org>]

janhoy commented on issue #85:
URL: https://github.com/apache/solr-operator/issues/85#issuecomment-1301476051

   First question is - should it be a configSet bootstrapping feature that will only be run on first startup if a configset with that name does not already exist...
   
   OR - should it be a mechanism to manage configset updates through the operator?
   
   As a bootstrapping feature we just need an initContainer which looks for a CM and uploads it with a CLI command.
   
   But as a management feature it would more look like a `SolrConfigSet` CRD, where you could create, update, delete. For this to make sense, Solr should supported making a configSet Read-Only, so it is "owned" by the operator, since changes from ConfigSet API would be overwritten on next CM change...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org