You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@pghalliday, you were so gracious and expedient with fix for Issue 3 that am encourage to ask for one more feature. The jdbc resource is nice and all but it pretty limitted. It would be great if there was a general purpose resource for setting any value in the config file, or ideally a block of config values all at once (for example the sonar.security and ldap values for the LDAP plugin)
A simpler though less handy solution would simply be to expose the location of the install as node property so that we can get at the /conf directory ourselves without needing any magic knowledge of the internals of the sonarqube cookbook.
Now I am asking for the moon, but to completely round out this cookbook, a resource to set properties stored on the properties table in the database, and the ability to set encrypted property values would be killer features. ;-)
The text was updated successfully, but these errors were encountered:
I have a tendency to only implement features I use, however I do accept merge requests ;) (also on vacation right now so won't likely look at this for a few days)
@pghalliday, you were so gracious and expedient with fix for Issue 3 that am encourage to ask for one more feature. The
jdbc
resource is nice and all but it pretty limitted. It would be great if there was a general purpose resource for setting any value in the config file, or ideally a block of config values all at once (for example thesonar.security
andldap
values for the LDAP plugin)A simpler though less handy solution would simply be to expose the location of the install as node property so that we can get at the
/conf
directory ourselves without needing any magic knowledge of the internals of the sonarqube cookbook.Now I am asking for the moon, but to completely round out this cookbook, a resource to set properties stored on the properties table in the database, and the ability to set encrypted property values would be killer features. ;-)
The text was updated successfully, but these errors were encountered: