Persisting state for incrementing counter
I am using getResource and setResource for persisting a counter value across script executions. Here is the code:
I did not use get/setState for a variety of reasons, but maybe that will have to change. The problem I just now realized is that this particular resource is now part of my git repo, which means the running incremented counter will get overwritten with each deploy. Our syncs only include
I did not use get/setState for a variety of reasons, but maybe that will have to change. The problem I just now realized is that this particular resource is now part of my git repo, which means the running incremented counter will get overwritten with each deploy. Our syncs only include
--skip-secrets right now. Maybe the answer is that we should just not include any resources in our repo at all? I think that is it. (I'm answering my own question as I'm describing the problem). So - is that best practice - no resources or secrets go into the repo?