ability to update request data upon successful deploy #971
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tpetr updated the field names and such here. Took another look and I didn't see any more places where we would get conflicts between the two sources of request data.
Would like to get @wsorenson 's thoughts as well to make sure I'm not missing anything.
My initial concern was that we then have possibly stale request data that hangs around and isn't correct. The deploy data is saved in history, but if the request is updated, we have out of date data hanging around. The deploy parent data is only around during the time the deploy is actually running as part of the pending deploy.