# \[Anaconda Blog\] condarc merge example incorrect?

**URL:** <https://forum.anaconda.com/t/anaconda-blog-condarc-merge-example-incorrect/64447>\
**Category:** Bugs & Issues\
**Created:** [November 10, 2023, 6:33pm UTC](https://forum.anaconda.com/t/anaconda-blog-condarc-merge-example-incorrect/64447 "2023-11-10T18:33:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![conpierce8](https://avatars.discourse-cdn.com/v4/letter/c/f5a800/32.png) [@conpierce8](https://forum.anaconda.com/u/conpierce8)\
**Post date:** [November 10, 2023, 6:33pm UTC](https://forum.anaconda.com/t/anaconda-blog-condarc-merge-example-incorrect/64447/1 "2023-11-10T18:33:36Z")

</div>

The example which demonstrates merging of map configuration parameters on [this post](https://www.anaconda.com/blog/conda-configuration-engine-power-users) on the Anaconda Blog is confusing, which (I think) is because it is incorrect.

Based on this:

> the merged settings will be
> 
> ```yaml
> proxy_servers: 
> https: https://prod-proxy
> 
> ```
> 
> with no `http` key defined.

I think the `~/.conda/condarc.d/proxies.yml` file should have one `http` key and one `https` key, rather than two `https` keys.

See the page with highlighted changes (made through my Vivaldi Developer Tools) that I think are needed:

 ![Corrected](https://europe1.discourse-cdn.com/anaconda/original/2X/5/5027e5a6bcd206d5be69a1c4b5c32485a4b097ea.jpeg)