Skip to content
This repository has been archived by the owner on Oct 19, 2023. It is now read-only.

Define data access layer #49

Open
athompson-r7 opened this issue Sep 21, 2015 · 2 comments
Open

Define data access layer #49

athompson-r7 opened this issue Sep 21, 2015 · 2 comments

Comments

@athompson-r7
Copy link
Contributor

We need to get something in place that will allow us to swap between direct communication with cloudformation and our own storage layer.

@athompson-r7 athompson-r7 added this to the 1.0 milestone Sep 21, 2015
@erran-r7
Copy link
Contributor

@athompson-r7 @jmanero-r7 @bcall-r7 @bturner-r7 @eciramella-r7 Thoughts on the need of a storage layer? We have a non-persistent level of storage. I'm assuming the storage we refer to in this issue would be more similar to Terraform's execution plan concept.

@athompson-r7
Copy link
Contributor Author

We might want to close this. I don't have a clue what the intent here was :/

I assume it had something to do with some caching service.

@erran-r7 erran-r7 modified the milestone: 1.0 Sep 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants