-
Notifications
You must be signed in to change notification settings - Fork 258
Labels
kind/taskWork that's part of an ongoing epicWork that's part of an ongoing epicneeds-triageNeeds attention from the triage teamNeeds attention from the triage teamresolution/fixedThis issue was fixedThis issue was fixed
Description
- The packages concepts page appears under concepts in the nav, but it's under guides in the filesystem. Move it under concepts in the file system.
- The packages concepts page needs instructions that say
pulumi installis the right way to install packages (as opposed tonpm i, etc.) b/c it will handle all references, whether they are inpackage.json(or whatever your supported package manager uses to include dependencies) and any local packages inPulumi.yaml. We could either separate the topics of adding references to packages and installing packages, or put them together - whatever reads best. - Make sure the guidance is summarized before we go into depth:
- Add references for any external libraries or Pulumi packages that have published SDKs with the standard package manager methods (e.g.
npm i, adding a line torequirements.txt, etc.) - Add references to Pulumi local packages (components, Any TF provider, etc.) via
pulumi package add. - Install packages (e.g. after cloning a repository) with
pulumi install.
- Add references for any external libraries or Pulumi packages that have published SDKs with the standard package manager methods (e.g.
- Check for other places where we talk about using
pulumi package addand ensure thatpulumi installis mentioned as the right way to install dependencies downstream.
Metadata
Metadata
Assignees
Labels
kind/taskWork that's part of an ongoing epicWork that's part of an ongoing epicneeds-triageNeeds attention from the triage teamNeeds attention from the triage teamresolution/fixedThis issue was fixedThis issue was fixed