From 72e92c9b54b81cd1cd7c84096cef99e2399d0274 Mon Sep 17 00:00:00 2001 From: Logan McDonald Date: Wed, 12 Oct 2022 10:20:56 -0400 Subject: [PATCH] be more explicit in rotation docs about what cups and uups stands for (#158) --- docs/operations/runbooks/rotate_application_secrets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/operations/runbooks/rotate_application_secrets.md b/docs/operations/runbooks/rotate_application_secrets.md index b4c2a4746..046991e19 100644 --- a/docs/operations/runbooks/rotate_application_secrets.md +++ b/docs/operations/runbooks/rotate_application_secrets.md @@ -23,14 +23,14 @@ Where `credentials-.json` looks like: You can see the current environment with `cf env `, for example `cf env getgov-unstable`. -The command `cups` stands for [create user provided service](https://docs.cloudfoundry.org/devguide/services/user-provided.html). User provided services are the way currently recommended by Cloud.gov for deploying secrets. The user provided service is bound to the application in `manifest-.json`. +The commands `cups` and `uups` stand for [`create user provided service`](https://docs.cloudfoundry.org/devguide/services/user-provided.html) and `update user provided service`. User provided services are the way currently recommended by Cloud.gov for deploying secrets. The user provided service is bound to the application in `manifest-.json`. To rotate secrets, create a new `credentials-.json` file, upload it, then restage the app. Example: ```bash -cf cups getgov-credentials -p credentials-unstable.json +cf update-user-provided-service getgov-credentials -p credentials-unstable.json cf restage getgov-unstable --strategy rolling ```