Skip to content

Commit 5e02af6

Browse files
authored
Add /n removal command for .teamcity/USE_CONFIG_WITH_TEAMCITY.md doc (GoogleCloudPlatform#13740)
1 parent d49966c commit 5e02af6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

mmv1/third_party/terraform/.teamcity/USE_CONFIG_WITH_TEAMCITY.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ The next step is provide some input values that the configuration needs to fully
5151
* Click on the `Context Parameters` tab at the top of the page
5252
* On this page you can add key:value pairs, which are used as input to the configuration in `.teamcity/settings.kts`
5353
* First, we need to enter credentials information in a special way that keeps the values secure. Here is the process for the credentials to the GA nightly test project:
54-
* Find the credentials JSON file for that project, ensure that the value has no newlines
54+
* Find the credentials JSON file for that project, ensure that the value has no newlines (Running `cat CREDENTIALS.json | tr -s '\n' ' '` will remove newline characters from your JSON key file)
5555
* Click the dropdown menu next to `Actions` in the top right and click `Generate token for a secure value...`
5656
* Paste the credentials JSON string into the `Secure value` field nd click `Generate Token`.
5757
* Copy the value shown below the field, which should look like `credentialsJSON:<uuid>`
@@ -145,4 +145,4 @@ In scenarios liek this, you will see an error shown at the bottom of the `Versio
145145
To avoid bugs reaching TeamCity, validate all changes to the TeamCity configuration files locally before merging a PR:
146146
* Generate the GA provider from Magic Modules
147147
* In the GA provider repo, run `cd .teamcity`
148-
* Validate the configuration using `make validate`
148+
* Validate the configuration using `make validate`

0 commit comments

Comments
 (0)