v2.0.0 #122
Replies: 3 comments 14 replies
-
Amazing work @markusthoemmes !! This is awesome - super appreciate the updated README.md, lots of cool functionality I wouldn't have figured out otherwise 🎉 |
Beta Was this translation helpful? Give feedback.
-
Can you explain how to use these? I'm really struggling to understand how to update for v2 where I only want to make a new deploy with an updated image. |
Beta Was this translation helpful? Give feedback.
-
Is it expected that environment variables have to be defined in the new And also feels a bit weird that I now have to store all the environment variables used in the DO app on GitHub and have them injected into the app spec, unless I'm doing something wrong. |
Beta Was this translation helpful? Give feedback.
-
This is a complete rewrite with the goal of being more orchestratable in a broader GitHub Actions context.
🚀 New Features
godo
instead of shelling out todoctl
for better error handling and overall control of the process.app.yaml
(defaults to.do/app.yaml
, configurable via theapp_spec_location
input) to create the app from instead of having to rely on an already existing app that's then downloaded (though that is still supported). The in-filesystem app spec can also be templated with environment variables automatically (see examples below).print_build_logs
andprint_deploy_logs
) and surfaces them as outputsbuild_logs
anddeploy_logs
.app
.Breaking changes:
images
input is no longer supported. Instead, use env-var-substitution for an in-repository app spec or theIMAGE_DIGEST_$component-name
/IMAGE_TAG_$component-name
environment variables to change the respective fields of images in an existing app.👨🏼💻 Contributors
@markusthoemmes
This discussion was created from the release v2.0.0.
Beta Was this translation helpful? Give feedback.
All reactions