# Question about stack API

**URL:** <https://forums.suse.com/t/question-about-stack-api/4305>\
**Category:** Rancher 1.x\
**Created:** [October 13, 2016, 9:20pm UTC](https://forums.suse.com/t/question-about-stack-api/4305 "2016-10-13T21:20:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnrengelman](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/johnrengelman/32/134_2.png) [@johnrengelman](https://forums.suse.com/u/johnrengelman)\
**Post date:** [October 13, 2016, 9:20pm UTC](https://forums.suse.com/t/question-about-stack-api/4305/1 "2016-10-13T21:20:59Z")

</div>

I’m working on integrating Rancher with Terraform and I’ve got 1 last item to implement: stack upgrades.  
It seems that the `docker_compose` and `rancher_compose` fields for a stack (or environment in v1) get populated with the raw, un-interpolated contents from a catalog entry when creating a stack from a catalog entry, but when you upgrade the stack to a newer version of the catalog entry, those values are not changed.

When calling the API to do a stack upgrade and passing an explicit `docker_compose` and `rancher_compose`, the values are not updated either, yet somehow the `exportConfig` action on the stack, returns the correct, interpolated file contents.  
This is making it difficult to detect modifications to these resources from Terraform’s perspective and I’m just wondering if I’m missing something here.