You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2022/02/23 06:32:00 UTC
[jira] [Resolved] (CAMEL-17698) Inconsistency in naming parts of camel-google-secrets-manager
[ https://issues.apache.org/jira/browse/CAMEL-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino resolved CAMEL-17698.
--------------------------------------
Resolution: Fixed
> Inconsistency in naming parts of camel-google-secrets-manager
> -------------------------------------------------------------
>
> Key: CAMEL-17698
> URL: https://issues.apache.org/jira/browse/CAMEL-17698
> Project: Camel
> Issue Type: Task
> Affects Versions: 3.16.0
> Reporter: David Jencks
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 3.16.0
>
>
> There's a lot of inconsistency about whether it's google-secret-manager or google-secrets-manager. Right now this has broken the website build because the spring-boot json file is google-secrets-manager.json but the camel components adoc has
> :camel-spring-boot-name: google-secret-manager
> Before this gets released I suggest that EVERYTHING be named consistently, either singular or plural but NOT a mixture.
> From e.g.
> ```
> import com.google.cloud.secretmanager.v1.SecretManagerServiceClient;
> ```
> it looks like google prefers a singular form, so I'd guess it would be less confusing for camel to adopt the same.
> I don't have a great deal of time right now but if there's agreement on what to do I can try to come up with a PR.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)