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.

Sign up for GitHub

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

Jump to bottom

When displaying values in pulumi config, add a column for "source" #731

Closed
lindydonna opened this issue Dec 15, 2017 · 1 comment
Closed

When displaying values in pulumi config, add a column for "source" #731

lindydonna opened this issue Dec 15, 2017 · 1 comment
Assignees
@ellismg
Labels
area/cli UX of using the CLI (args, output, logs) impact/usability Something that impacts users' ability to use the product easily and intuitively
Milestone
0.11

Comments

@lindydonna
Copy link

Something like

KEY VALUE SOURCE
aws:config:region us-west-2 ./Pulumi.yaml
foo bar workspace MyWorkspace
foo bar Stack MyStack
@lindydonna lindydonna added impact/usability Something that impacts users' ability to use the product easily and intuitively area/cli UX of using the CLI (args, output, logs) labels Dec 15, 2017
@ellismg ellismg self-assigned this Jan 15, 2018
@ellismg ellismg added this to the 0.11 milestone Jan 15, 2018
@lindydonna
Copy link
Author

Can be closed once #866 is done.

ellismg added a commit that referenced this issue Feb 28, 2018
@ellismg
Rework configuration model
dbe378d 
This change updates our configuration model to make it simpler to
understand by removing some features and changing how things are
persisted in files.

Notable changes:

- We've removed the notion of "workspace" vs "project"
  config. Now, configuration is always stored in a file next to
  `Pulumi.yaml` named `Pulumi.<stack-name>.yaml` (the same file we'd
  use for an other stack specific information we would need to persist
  in the future).
- We've removed the notion of project wide configuration. Every new
  stack gets a completely empty set of configuration and there's no
  way to share common values across stacks, instead the common value
  has to be set on each stack.

We retain some of the old code for the configuration system so we can
support upgrading a project in place. That will happen with the next
change.

This change fixes some issues and allows us to close some
others (since they are no longer possible).

Fixes #866
Closes #872
Closes #731
ellismg added a commit that referenced this issue Mar 1, 2018
@ellismg
Rework configuration model
9f25ddb 
This change updates our configuration model to make it simpler to
understand by removing some features and changing how things are
persisted in files.

Notable changes:

- We've removed the notion of "workspace" vs "project"
  config. Now, configuration is always stored in a file next to
  `Pulumi.yaml` named `Pulumi.<stack-name>.yaml` (the same file we'd
  use for an other stack specific information we would need to persist
  in the future).
- We've removed the notion of project wide configuration. Every new
  stack gets a completely empty set of configuration and there's no
  way to share common values across stacks, instead the common value
  has to be set on each stack.

We retain some of the old code for the configuration system so we can
support upgrading a project in place. That will happen with the next
change.

This change fixes some issues and allows us to close some
others (since they are no longer possible).

Fixes #866
Closes #872
Closes #731
@ellismg ellismg closed this as completed in 207a975 Mar 2, 2018
@ellismg ellismg mentioned this issue Mar 2, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ellismg ellismg

Labels
area/cli UX of using the CLI (args, output, logs) impact/usability Something that impacts users' ability to use the product easily and intuitively
Projects
None yet
Milestone
0.11
Development

No branches or pull requests
2 participants
@lindydonna @ellismg