Skip to content

Instantly share code, notes, and snippets.

@vjeffrey
Created January 31, 2019 17:20
Show Gist options
  • Save vjeffrey/3c1b990b90edc8921e1f7caf342dc0a5 to your computer and use it in GitHub Desktop.
Save vjeffrey/3c1b990b90edc8921e1f7caf342dc0a5 to your computer and use it in GitHub Desktop.
timeline
- october 2018: issue opened for inherited profiles with inspec 1 causing duplicated controls in a2
- late october 2018: customer is advised to update inspec to 2+, as changes needed will not be backported to inspec 1
- december 2018: ticket opened for sigsegv failure on ingested inspec 1 reports https://getchef.zendesk.com/agent/tickets/20892
- corresponding ticket created in github: https://github.com/chef/a2/issues/4494
- the decision is made, in conversations and on github issues, to update the code to reject inspec 1x reports
- pr is created to implement that logic: https://github.com/chef/a2/pull/4538 (dec 11th)
- some communication of the change happens in support-team: https://chefio.slack.com/archives/C07JNP4LU/p1545335412116200
- change was noted in readiness mtg and marked in notes: https://docs.google.com/document/d/1x7Xn0YLTF8QTyY7Yru5lL0xe_MFeKrUFQU8_hE9yq2s/edit#
- change was released on january 22
- optum filed ticket: https://getchef.zendesk.com/agent/tickets/21270
- discussions happened, we decided to remove the code that rejects reports with inspec 1x
- jay got a pr up: https://github.com/chef/a2/pull/4792
- customers were given a special command to get the fix before it was released to current due to severity of issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment