Merge lp:~niemeyer/pyjuju/go-formula-bundle into lp:pyjuju/go
Proposed by
Gustavo Niemeyer
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Gustavo Niemeyer | ||||
Approved revision: | 23 | ||||
Merged at revision: | 10 | ||||
Proposed branch: | lp:~niemeyer/pyjuju/go-formula-bundle | ||||
Merge into: | lp:pyjuju/go | ||||
Prerequisite: | lp:~niemeyer/pyjuju/go-formula-dir | ||||
Diff against target: |
309 lines (+245/-4) 6 files modified
formula/Makefile (+1/-0) formula/bundle.go (+161/-0) formula/bundle_test.go (+66/-0) formula/dir.go (+1/-1) formula/dir_test.go (+1/-3) formula/formula_test.go (+15/-0) |
||||
To merge this branch: | bzr merge lp:~niemeyer/pyjuju/go-formula-bundle | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Kapil Thangavelu (community) | Approve | ||
Review via email: mp+75247@code.launchpad.net |
Description of the change
Go port must support formula bundles
In addition to formula directories, the Go port
must support formula bundles.
To post a comment you must log in.
[0] I don't see any verification of exec bits on scripts which we need to execute hooks from extracted formulas. On unixie platforms, in the python impl, we read off extra bits stored in the zip info entry, which seems to be common for unix zip tools, albeit outside of the zip standard.
[1] ReadBundleBytes reads the whole file into memory, which for naive usage of the amazon api is needed, but that seems like something that would be better exposed via a file path to the zip file and incorporate directly into the provider storage usage, rather than as an api on the bundle. What's the reasoning for exposing this api directly on the bundle?
[2] ReadAt seems to be untested, the comment on why its awesome escapes me. The construction also seems odd, although thats probably my lack of go knowledge, its a public method returning a private type?
[3] Due to the changes in formula-dir (filepath.Rel) i'm unable to run the tests for this.