-
Notifications
You must be signed in to change notification settings - Fork 207
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
Update docs website to link to the new 0.9.13 SDK #75
Conversation
This also updates the Changelog to discuss the two new features.
I will not merge or deploy this until we have updated LM's PPCs to 0.9.13 and are ready to share the new SDK with them, but I am opening this now to give @lindydonna ample time to wordsmith my terrible prose into something acceptable. /cc @joeduffy as an FYI, since I wrote about his feature. |
@ellismg LGTM. I'll probably wordsmith a bit more when I do the 0.10 notes, but it's clear and understandable. I'm glad you added info on the docker feature, because that was one of the missing items in the changelog spreadsheet! :) |
@@ -1,7 +1,7 @@ | |||
--- | |||
layout: default | |||
nav_section: "install" | |||
installer_version: "0.9.11" | |||
installer_version: "0.9.13" |
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.
When do we start publishing all prior builds? If a team is on version X, then they may want other teammates to go download version X, rather than only having the latest version.
It would be excellent if this came with links to release notes specific to that release also, e.g.
Version | Date | Changelog | Download |
---|---|---|---|
0.9.13 | 2/6/18 | Link | Link |
0.9.11 | 2/2/18 | Link | Link |
... |
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.
I like this idea. Even if the changelog is one big file (which I prefer), we can use anchor tags. I'll file a new issue.
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.
Note that we do retain the old SDKs (even though we remove links to them) so a customer today could copy/paste the link and change the version number in it to get older bits.
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.
👍
|
||
- Added the ability to control the upload context to the Pulumi Service. You may now set a `context` property in `Pulumi.yaml`, which is combined with the location of `Pulumi.yaml`. This new path is the root of what is uploaded and can be used during deployment. This allows you to, for example, share common code that is located in a folder in your source tree above the directory `Pulumi.yaml` for the project you are deploying. | ||
|
||
- Added additional configuration for docker builds for a container. The `build` property of a container may now either be a string (which is treated as a path to the folder to do a `docker build` in) or an object with properties `context`, `dockerfile` and `args`, which are passed to `docker build`. If unset, `context` defaults to the current working directory, `dockerfile` defaults to `Dockerfile` and `args` default to no arguments. |
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.
If you want to add more detail on what these settings do, see https://docs.docker.com/compose/compose-file/#build which is what we used for inspiration.
This also updates the Changelog to discuss the two new features.