Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Gheorghe Popescu Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.115053.1610614920033%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Gheorghe Popescu Fix Version/s: FACT 4.0.48 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.115044.1610614680075%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ghost-18.12, ready for triage 3 ghost-13.01.2020 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.107469.1609834680053%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ghost-18.12 , ready for triage 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.104201.1608310620303%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ready for triage 2 ghost-19.12 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.96908.1607939460081%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.89289.1606894740215%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.86932.1606336920097%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Sebastian Miclea Create a cache file with a tested fact in the Facter 3 format. In facter.conf set the same fact to be cached by Facter 4 with a large TTLS * run Facter 4 with cache configured ** check if the cache file was invalidated and recreated by Facter 4 ** check the cache file contains "cache_format_version": 1 ** check the fact value was written to the cache ** check that the old value from the Facter 3 formatted cache is no longer in the cache * run Facter 4 with no config file ** check we have a fact value and it is read from the system ** check the cache file was not changed * run Facter 4 with config ** check the cache file did not changed change ** check it prints the value from the cache Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.86568.1606313040399%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ready for triage ghost 25.11 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.378290.1605282375000.81976.1605708840127%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Create a cache file with a tested fact in the Facter 3 format. In facter.conf set the same fact to be cached by Facter 4 with a large TTLS - * run Facter 4 with cache configured - ** check if the cache file was invalidated and recreated by Facter 4 - ** check the cache file contains "cache_format_version": 1 - ** check the fact value was written to the cache - ** check that the old value from the Facter 3 formatted cache is no longer in the cache - * run Facter 4 with no config file - ** check we have a fact value and it is read from the system - ** check the cache file was not changed - * run Facter 4 with config - ** check the cache file did not changed - ** check it prints the value from the cache Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Create a cache file with a tested fact in the Facter 3 format. In facter.conf set the same fact to be cached by Facter 4 with a large TTLS - run Facter 4 with cache configured - check if the cache file was invalidated and recreated by Facter 4 - check the cache file contains "cache_format_version": 1 - check the fact value was written to the cache - check that the old value from the Facter 3 formatted cache is no longer in the cache - run Facter 4 with no config file - check we have a fact value and it is read from the system - check the cache file was not changed - run Facter 4 with config - check the cache file did not changed - check it prints the value from the cache Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Issue Type: Task Assignee: Unassigned Created: 2020/11/13 7:46 AM Priority: Normal Reporter: Bogdan Irimie Create a cache file with a tested fact in the Facter 3 format. In facter.conf set the same fact to be cached by Facter 4 with a large TTLS run Facter 4 with cache configured check if the cache file was invalidated and recreated by Facter 4 check the cache file contains "cache_format_version": 1 check the fact value was written to the cache check that the old value from the Facter 3 formatted cache is no longer in the cache run Facter 4 with no config file check we have a fact value and it is read from the system check the cache file was not changed run Facter 4 with config check the cache file did not changed check it prints the value from the cache
