# YML files for Projects

**URL:** <https://forums.suse.com/t/yml-files-for-projects/15820>\
**Category:** SUSE Rancher Prime\
**Created:** [November 13, 2019, 5:26pm UTC](https://forums.suse.com/t/yml-files-for-projects/15820 "2019-11-13T17:26:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gonzalo.martinez](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gonzalo.martinez](https://forums.suse.com/u/gonzalo.martinez)\
**Post date:** [November 13, 2019, 5:26pm UTC](https://forums.suse.com/t/yml-files-for-projects/15820/1 "2019-11-13T17:26:18Z")

</div>

Hello guys.

Is there any way to create projects in Rancher programatically, and not using the UI?

Preferable YML files, as they are easier to manage with Git.

Best regards

---

<div class="post-metadata">

**Author:** ![Fraser\_Goffin](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/fraser_goffin/32/6608_2.png) [@Fraser\_Goffin](https://forums.suse.com/u/Fraser_Goffin)\
**Post date:** [November 19, 2019, 10:17pm UTC](https://forums.suse.com/t/yml-files-for-projects/15820/2 "2019-11-19T22:17:11Z")

</div>

Terraform using the Rancher2 provider.

---

<div class="post-metadata">

**Author:** ![MSandro](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/msandro/32/5032_2.png) [@MSandro](https://forums.suse.com/u/MSandro)\
**Post date:** [November 26, 2019, 2:33pm UTC](https://forums.suse.com/t/yml-files-for-projects/15820/4 "2019-11-26T14:33:33Z")

</div>

I found an easy solution using the rancher cli.  
./rancher-cli projects create

---

<div class="post-metadata">

**Author:** ![gonzalo.martinez](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gonzalo.martinez](https://forums.suse.com/u/gonzalo.martinez)\
**Post date:** [November 26, 2019, 2:51pm UTC](https://forums.suse.com/t/yml-files-for-projects/15820/5 "2019-11-26T14:51:19Z")

</div>

I ended up using Rancher’s API with curl.

Rancher is a great tool, but the lack of documentation kills all its potential.

---

<div class="post-metadata">

**Author:** ![Fraser\_Goffin](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/fraser_goffin/32/6608_2.png) [@Fraser\_Goffin](https://forums.suse.com/u/Fraser_Goffin)\
**Post date:** [December 1, 2019, 11:23pm UTC](https://forums.suse.com/t/yml-files-for-projects/15820/6 "2019-12-01T23:23:14Z")

</div>

How can having an API that is completely open, integrated with the UI, and easy to interrogate programmatically be considered as lacking documentation. The point about an API is that it doesn’t try to anticipate every possible use case, but instead provides an intuitive model for requesting information or making changes in system state. The Rancher API fulfils that goal IMHO.
