We generally want examples and apps to be authored such that they are clonable/deployable as-is without using new/up (and want to encourage this). That means no longer using the ${PROJECT} and ${DESCRIPTION} replacement strings in Pulumi.yaml and other text files. Instead, good default project names and descriptions should be specified in Pulumi.yaml and elsewhere. We'll use the specified values as defaults when prompting the user, and then directly serialize/save the values to Pulumi.yaml when configuring the user's project. This does mean that name in package.json (for nodejs projects) won't be updated if it isn't using ${PROJECT}, but that's OK. Our templates in the pulumi/templates repo will still use ${PROJECT}/${DESCRIPTION} for now, to continue to work well with v0.15 of the CLI. After that version is no longer in use, we can update the templates to no longer use the replacement strings and delete the code in the CLI that deals with it. |
||
---|---|---|
.. | ||
apitype | ||
backend | ||
diag | ||
encoding | ||
engine | ||
graph | ||
operations | ||
resource | ||
testing | ||
tokens | ||
tools | ||
util | ||
version | ||
workspace |