-
Notifications
You must be signed in to change notification settings - Fork 232
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
Updates for 0.12.1 #254
Updates for 0.12.1 #254
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,17 +13,22 @@ | |
"title": "Documentation", | ||
"icon": "library_books", | ||
"items": [ | ||
{ "title": "Introduction", "url": "https://docs.pulumi.com/reference/" }, | ||
{ "title": "Concepts", "url": "https://docs.pulumi.com/reference/concepts.html" }, | ||
{ "title": "Programming Model", "url": "https://docs.pulumi.com/reference/programming-model.html" }, | ||
{ "title": "Learn about AWS", "url": "https://docs.pulumi.com/reference/aws.html" }, | ||
{ "title": "Learn about Kubernetes", "url": "https://docs.pulumi.com/reference/kubernetes.html" } | ||
{ "title": "Introduction", "url": "https://docs.pulumi.com/concepts/" }, | ||
{ "title": "Programming Model", "url": "https://docs.pulumi.com/concepts/programming-model.html" }, | ||
{ "title": "Reference", "url": "https://docs.pulumi.com/reference" }, | ||
{ "title": "Learn about AWS", "url": "https://docs.pulumi.com/concepts/aws.html" }, | ||
{ "title": "Learn about Kubernetes", "url": "https://docs.pulumi.com/concepts/kubernetes.html" } | ||
] | ||
}, | ||
"news": { | ||
"title": "News", | ||
"icon": "radio", | ||
"items": [ | ||
{ | ||
"title": "Pulumi 0.12.1 now available", | ||
"url": "https://docs.pulumi.com/install/changelog.html#v121", | ||
"date": "2018-05-09" | ||
}, | ||
{ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we unpublish 0.12.0, so we don't have any risk that LM will pick it up? (Or at least, not advertise it on this page?) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. From a changelog and News perspective I wouldn't remove it - as it's part of the history of improvements. We will not provide any direct links to download We could choose to unpublish as well if we want to be really paranoid. We shoudl wait until after we merge these changes so that links from docs site continue workin. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok... but you have to realize there's a non-zero risk someone from LM is going to accidentally download it, and we will be left dealing with the fallout of previews doing updates ... may not happen, but given that Lucas already tried to roll ahead to 0.11.x, I wouldn't discount the possibility. If we're doing this, by the way -- which I almost always agree with except for builds we've published that we explicitly know are trash -- why did all the historical versions go away? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure precisely which piece of content you are concerned about here. The dashboard news feed - which this comment is attached to - has only existed since The only links to historical downloads are at the top of the changelog, and only to the latest 0.10, 0.11 and 0.12 release respectively. So after these changes are merged, to my knowledge, there will be no links from this site to download There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you should just merge as-is if there's no download link they might find. |
||
"title": "Pulumi 0.12.0 now available", | ||
"url": "https://docs.pulumi.com/install/changelog.html#v120", | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,9 +23,9 @@ title: "Change Log" | |
</thead> | ||
<tbody> | ||
<tr> | ||
<th scope="row"><a href="#v120">0.12.0</a></th> | ||
<td>2018/04/26</td> | ||
<td>{% include sdk-links.html version='0.12.0' %}</td> | ||
<th scope="row"><a href="#v121">0.12.1</a></th> | ||
<td>2018/05/09</td> | ||
<td>{% include sdk-links.html version='0.12.1' %}</td> | ||
</tr> | ||
<tr> | ||
<th scope="row"><a href="#v113">0.11.3</a></th> | ||
|
@@ -42,6 +42,32 @@ title: "Change Log" | |
|
||
> See [known issues](../reference/known-issues.html) for currently known issues and workarounds. | ||
|
||
## v0.12.1 {#v121} | ||
|
||
Released on May 9, 2018 | ||
|
||
### Added | ||
|
||
- A new all-in-one installer script is now available at https://get.pulumi.com. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit, I noticed that As such, and probably a good idea either way, I think I'd hyperlink this text to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Good idea. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
It was not intentional. I suspect the reason this is happening is that the CloudFront is returning a different content type ( Opened: pulumi/get.pulumi.com#5 |
||
|
||
- Many enhancements to `pulumi new` ([pulumi/pulumi#1307](https://github.com/pulumi/pulumi/pull/1307)). The command now interactively walks through creating everything needed to deploy a new stack, including selecting a template, providing a name, creating a stack, setting default configuration, and installing dependencies. | ||
|
||
- Several improvements to the `pulumi update` CLI experience ([pulumi/pulumi#1260](https://github.com/pulumi/pulumi/pull/1260)): a tree view display, more details from logs during deployments, and rendering of stack outputs at the end of updates. | ||
|
||
- A new `@pulumi/aws-infra` package is available which contains useful AWS infrastructure components for `Network` and `Cluster` (([pulumi/pulumi-cloud#472](https://github.com/pulumi/pulumi-cloud/pull/472)). | ||
|
||
### Changed | ||
|
||
- (**Breaking**) Removed the `LogCollector` and `onError` handler from `@pulumi-cloud` ([pulumi/pulumi-cloud#474](https://github.com/pulumi/pulumi-cloud/pull/474)). These were previously created in all stacks using `@pulumi/cloud`, but in practice were not being used. | ||
|
||
### Fixed | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I still long for a more complete list of commits. This list looks far more sparse than it ought to. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We could add this? The majority of these are internal engineering things and most users do not have access to any of the links - but if we want to advertise the volume of work, this will do that. Commitspulumi/pulumi#1346: Fix preview against a PPC There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This feels nice from an open source transparency perspective. Let's do it. |
||
|
||
- Significant performance improvements for `pulumi update` ([pulumi/pulumi#1319](https://github.com/pulumi/pulumi/pull/1319)). | ||
|
||
- JavaScript `async` functions in Node 7.6+ now work with Pulumi function serialization ([pulumi/pulumi#1311](https://github.com/pulumi/pulumi/pull/1311). | ||
|
||
- Support installation on Windows in folders which contain spaces in their name ([pulumi/pulumi#1300](https://github.com/pulumi/pulumi/pull/1300)). | ||
|
||
## v0.12.0 {#v120} | ||
|
||
Released on April 26, 2018 | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
title: "Installation and Setup" | ||
installer_version: "0.12.0" | ||
installer_version: "0.12.1" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Minor comment about this page: The "The current SDK version is XX" should probably come between the Installation and Setup and Mac and Linux Easy Install header. It links to the changelog which is interesting no matter how you are installing the product. |
||
--- | ||
|
||
<!-- | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
0.12.0 | ||
0.12.1 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,19 +25,17 @@ In this tutorial, we'll show how to create a simple REST API that counts the num | |
// Create an API endpoint | ||
let endpoint = new cloud.HttpEndpoint("hello-world"); | ||
|
||
endpoint.get("/{route+}", (req, res) => { | ||
endpoint.get("/{route+}", async (req, res) => { | ||
let route = req.params["route"]; | ||
console.log(`Getting count for '${route}'`); | ||
|
||
// get previous value and increment | ||
let count; | ||
return counterTable.get({route}).then(value => { | ||
count = (value && value.count) || 0; | ||
return counterTable.insert( { route, count: ++count }); | ||
}).then(() => { | ||
res.status(200).json({ route, count}); | ||
console.log(`Got count ${count} for '${route}'`); | ||
}); | ||
let value = await counterTable.get({route}); // reference outer `counterTable` object | ||
let count = (value && value.count) || 0; | ||
await counterTable.insert( { route, count: ++count }); | ||
|
||
res.status(200).json({ route, count}); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit, super minor formatting issue, missing a space between |
||
console.log(`Got count ${count} for '${route}'`); | ||
}); | ||
|
||
module.exports.endpoint = endpoint.publish().url; | ||
|
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.
Do we want to to include links to Examples and Community Slack?