Skip to content
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

Merged
merged 1 commit into from
Feb 7, 2018

Conversation

ellismg
Copy link
Contributor

@ellismg ellismg commented Feb 7, 2018

This also updates the Changelog to discuss the two new features.

This also updates the Changelog to discuss the two new features.
@ellismg
Copy link
Contributor Author

ellismg commented Feb 7, 2018

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.

@lindydonna
Copy link
Contributor

@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"
Copy link
Member

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
...

Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor

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.
Copy link
Member

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.

@ellismg ellismg merged commit 648f7d9 into production Feb 7, 2018
@lindydonna lindydonna deleted the update-to-0.9.13 branch February 8, 2018 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants