New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parse package.json and section.config.json for better output, and replace logging pipeline #120
Conversation
8cb8015
to
5c1d9fc
Compare
log levels and timestamps in stdout. Much prettier.
9ce1bec
to
f1a2e90
Compare
bc85972
to
435e583
Compare
n, err := CIRead.Read(buf) | ||
if err != nil{ | ||
return err | ||
// if err := json.Unmarshal(sectionConfigContent.Bytes(), §ionConfig); err != nil { |
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.
Bit of commented out code
if moduleVersion == "unknown"{ | ||
log.Debug().Msg("failed to pair app path (aka proxy name) with image (version)") | ||
} | ||
// for proxy, _ := range sectionConfig["proxychain"]{ |
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.
Also here
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.
Reviewed on a call with Alice
The package.json can look something like this:
and running
sectionctl deploy
will work without specifying--accountid
(-a
),--appid
(-i
) or--environment
(-e
)furthermore the deploy will output the git repo URL and the tarball hash, as well as your nodejs module name and module version, based on the section.config.json and the
--AppPath
parameterThis also fixes the spinner flashing on windows terminal as per briandowns/spinner#116