> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/resources/rotate-passwords.md).

# Rotate Passwords

This document will explain how to rotate datasource passwords using the `sdm admin datasources update` command. You can also use this command to update any other aspects of your datasources.

### Get the JSON Template for your Datasource

StrongDM supports dozens of datasources, and each has its own import/update format. To get the current JSON state of the datasource you want to modify, run `sdm admin datasources list -j -e > update.json` command to get a JSON document that you can modify. This command will put information for all datasources into `update.json`.

### Example Update JSON

The `password` field is not included in the JSON export, but you can add it as seen below. Though each datasource type has a bunch of different fields, however, all you'll need is `name` and `password` for the purposes of password update. You can remove any fields you're not using.

{% hint style="info" %}
The `name` field must be unique for each datasource.
{% endhint %}

```json
[
  {
    "type": "postgres",
    "name": "postgres datasource",
    "password": "newPassword",
  },
  {
    "type": "mysql",
    "name": "mysql datasource",
    "password": "newPassword",
  }
]
```

### Run the Update

Once you have your modified JSON ready to go, you can update the password(s) (and any other fields you've modified) by running `sdm admin datasources update --file update.json`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.strongdm.com/admin/resources/rotate-passwords.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.