~axwalk/juju-core/lp1303195-manual-ubuntuuser-bash : changes

~axwalk/juju-core/lp1303195-manual-ubuntuuser-bash » Changes to testing/targz.go from revision 2662

From Revision 2662

Rev	Summary	Authors	Date
1988	[r=axwalk],[bug=1235717] Fix tools metadata generation for n... [r=axwalk],[bug=1235717] Fix tools metadata generation for null provider There's two functional changes here: - If there's existing tools metadata, use it if it has sha256/size in it, and the tools haven't been replaced. - Don't use net/http or the tools URL when fetching tools to compute sha256/size. That doesn't work with sshstorage. - Don't fetch existing tools to resolve metadata during normal tools syncing operations. Only the "juju metadata generate-tools" command will do this now. Additionally, I have refactored environs/tools/simplestreams.go, to make the intent of WriteMetadata (now MergeAndWriteMetadata) more obvious. That function is now composed of several other more specific functions. Fixes #1235717 https://codereview.appspot.com/14527043/	Andrew Wilkins	10 years ago
1877	[r=wallyworld] Validate tools using sha256 checksum [r=wallyworld] Validate tools using sha256 checksum The simplestreams tools metadata includes a sha256 checksum and the size of the tarball. When tools are unpacked, and when they are downloaded to the bootstrap node, the checksum is matched against the tarball and an error is raised if there is a mismatch. Legacy tools loading does not support checksums so tests needed to be changed accordingly. In so doing, some common tools helpers were moved to environs/testing/tools.go. This also has the benefit of keeping the tools related test code in one place, making it easier to swap out the legacy code later. https://codereview.appspot.com/13842044/	Ian Booth	10 years ago
1213	Add per-file copyright headers Add per-file copyright headers As requested during the release process for Ubuntu, we need a copyright statement at the top of source files. I have deliberately excluded documentation and non-go code for now, pending feedback. Because bzr already has a fancy tool for doing the years from the revision history, the year stated comes from there rather than being project-wide. R=rog, dimitern CC= https://codereview.appspot.com/9104045	Martin Packman	11 years ago
414	cmd/jujud: add Upgrader type. cmd/jujud: add Upgrader type. This conforms to the task interface as expected by runTasks, which should make it simple to add upgrading logic to agents. R=fwereade, niemeyer CC= https://codereview.appspot.com/6464074	Roger Peppe	11 years ago
410	cmd/jujud: add runTasks function and use it for agents. cmd/jujud: add runTasks function and use it for agents. This will make it easy to add new agent tasks such as upgrading. R=fwereade, TheMue, niemeyer, dfc CC= https://codereview.appspot.com/6458134	Roger Peppe	11 years ago
405	testing: move NewFile and Archive from environs/tools_test.g... testing: move NewFile and Archive from environs/tools_test.go ... renaming them to NewTarFile and TarGz. This makes it easier for other packages to implement tests that call environs.UnpackTools. R=niemeyer CC= https://codereview.appspot.com/6460092	Roger Peppe	11 years ago