Naming scheme for Drone orgsecrets #118

Open
opened 2021-08-16 17:34:17 +00:00 by 3wordchant · 0 comments
Owner

Currently, we have a mixture of formats:

<username>_<service>_access_token
<service>_reg_passwd[_<username>] / <service>_reg_username[_<username>]
drone_<service>_<host>
<username>_password

I think having some kind of standard might help:

  • easier to know what to call a new orgsecret?
  • easier to see if there's an existing one (to reuse it, or rotate it in an emergency)?

(And easier if we end up migrating Gitea again 😛)

What about (although no strong preferences, just a suggestion):

<service>[_<host>]_<username>_<type>

Which might make

  • matrix_chat.autonomic.zone_autono-bot_password
  • dockerhub_thecoopcloud_password (no <host>, implied by <service>)
  • drone_build.coopcloud.tech_coop-cloud_token

While we're at it, maybe we can standardise on either passwd or password for <type>? Prefer "password", but think either would be better than both 🧘

Currently, we have a mixture of formats: ``` <username>_<service>_access_token <service>_reg_passwd[_<username>] / <service>_reg_username[_<username>] drone_<service>_<host> <username>_password ``` I think having some kind of standard might help: - easier to know what to call a new orgsecret? - easier to see if there's an existing one (to reuse it, or rotate it in an emergency)? (And easier if we end up migrating Gitea again 😛) What about (although no strong preferences, just a suggestion): `<service>[_<host>]_<username>_<type>` Which might make - `matrix_chat.autonomic.zone_autono-bot_password` - `dockerhub_thecoopcloud_password` (no `<host>`, implied by `<service>`) - `drone_build.coopcloud.tech_coop-cloud_token` While we're at it, maybe we can standardise on either `passwd` or `password` for `<type>`? Prefer "password", but think either would be better than both 🧘
3wordchant added the
enhancement
question
documentation
ci/cd
labels 2021-08-16 17:34:17 +00:00
decentral1se added this to the Continuous integration testing for apps milestone 2021-09-09 14:26:50 +00:00
Sign in to join this conversation.
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#118
No description provided.