# Updating the admin console UI with the same release

**URL:** <https://community.replicated.com/t/updating-the-admin-console-ui-with-the-same-release/1037>\
**Category:** How do I?\
**Created:** [November 9, 2022, 11:40pm UTC](https://community.replicated.com/t/updating-the-admin-console-ui-with-the-same-release/1037 "2022-11-09T23:40:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jensese](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jensese](https://community.replicated.com/u/jensese)\
**Post date:** [November 9, 2022, 11:40pm UTC](https://community.replicated.com/t/updating-the-admin-console-ui-with-the-same-release/1037/1 "2022-11-09T23:40:21Z")

</div>

We are trying to patch the UI of the replicated KOTS admin console after the app is installed.

We’d like to automate dynamically adding values to fields (db server names).

I download our configs using `kubectl kots pull <app-slug>/<channel> --license-file /license.yaml --shared-password --config-values --namespace=default` to the `/root/<app-slug>/upstream` directory.

When I upload our config file that’s been modified, and run `kubectl kots install <app-slug>/<channel> --license-file /license.yaml --config-values config.yaml --namespace=default` the response is `Error: failed to parse config values: not config values`

The config file is pulled directly from the `kots pull` command and is formatted like we have in our repo.

(I saw alternatives, like creating a new release, but for our QA team they use release ids in their validation documentation sometimes.)

---

<div class="post-metadata">

**Author:** ![craig](https://avatars.discourse-cdn.com/v4/letter/c/ed8c4c/32.png) [@craig](https://community.replicated.com/u/craig)\
**Post date:** [November 10, 2022, 2:48pm UTC](https://community.replicated.com/t/updating-the-admin-console-ui-with-the-same-release/1037/2 "2022-11-10T14:48:39Z")

</div>

Hi @jensese, the error `Error: failed to parse config values: not config values` occurs when the file passed to the `--config-values` flag is not `apiVersion: kots.io/v1beta1` and `kind: ConfigValues`.

In this case the config values file would be downloaded to `/root/<app-slug>/upstream/userdata/config.yaml`. That is the file that can be edited and passed to the `--config-values` flag.

---

<div class="post-metadata">

**Author:** ![dex](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dex/32/26_2.png) [@dex](https://community.replicated.com/u/dex)\
**Post date:** [November 10, 2022, 6:35pm UTC](https://community.replicated.com/t/updating-the-admin-console-ui-with-the-same-release/1037/3 "2022-11-10T18:35:25Z")

</div>

Is there a reason you’re using `kots install` instead of `kots upload` ? You might also get value from `kots config set` as an alternative: [set config | Replicated Docs](https://docs.replicated.com/reference/kots-cli-set-config)

---

<div class="post-metadata">

**Author:** ![jensese](https://avatars.discourse-cdn.com/v4/letter/j/54ee81/32.png) [@jensese](https://community.replicated.com/u/jensese)\
**Post date:** [November 30, 2022, 7:44pm UTC](https://community.replicated.com/t/updating-the-admin-console-ui-with-the-same-release/1037/4 "2022-11-30T19:44:04Z")

</div>

Thanks Dex, I was updating the wrong config file, it was a couple directories deeper than I thought.

I couldn’t quite get `kots upload` to work.

We automate both applying a license, and updating config values in a single command, which seemed more straightforward to me.