prehistoric-account-60014
04/21/2020, 1:51 AM--yes
option. Is this intentional?gentle-diamond-70147
04/21/2020, 1:52 AMprehistoric-account-60014
04/21/2020, 1:53 AM--yes
will now fail.gentle-diamond-70147
04/21/2020, 1:57 AMprehistoric-account-60014
04/21/2020, 1:57 AMgentle-diamond-70147
04/21/2020, 1:59 AMprehistoric-account-60014
04/21/2020, 1:59 AMstrong-iron-54278
04/21/2020, 2:14 AMgentle-diamond-70147
04/21/2020, 2:18 AMversion
as part of the login command to pin the version.green-morning-1318
04/21/2020, 2:21 AMstrong-iron-54278
04/21/2020, 2:31 AMgreen-morning-1318
04/21/2020, 2:31 AMprehistoric-account-60014
04/21/2020, 3:18 PM--yes
to be implicit in CI. For example, could we set a PULUMI_NON_INTERACTIVE
env var to not have to pass --yes
?cool-egg-852
04/21/2020, 3:27 PM--yes
?prehistoric-account-60014
04/21/2020, 3:30 PM--yes
outside of the script’s context doesn’t make it clear where that argument is going. For example, we have npm scripts called deploy
but they might not all use Pulumi. Running npm deploy -- --yes
for all packages isn’t right since not all deploy scripts will expect that argument--yes
for us, but then we would have to do that for every Pulumi script and we would basically be implementing the feature we’re asking for ourselves. So I was just wondering if it could be provided by the CLI out of the box 🙂cool-egg-852
04/21/2020, 3:32 PMCI
env var, and if set, apply --yes
.CI
.prehistoric-account-60014
04/21/2020, 3:34 PMpulumi up
with this logic. Wouldn’t you agree that having some sort of environment variable would help?cool-egg-852
04/21/2020, 3:34 PMprehistoric-account-60014
04/21/2020, 3:37 PM"deploy": "pulumi up"
, we would need to do "deploy": "if [ \"PULUMI_NON_INTERACTIVE\" = true ]; then pulumi up --yes; else pulumi up; fi"
white-balloon-205
--yes
or --skip-preview
. For the latter you will want the interactive review workflow.
Can you give more detail on why you want a single pulumi up
command in scripts that covers both of these scenarios?cool-egg-852
04/21/2020, 4:19 PMdeploy:ci
script and then you don’t have to worry about it.prehistoric-account-60014
04/21/2020, 4:22 PMdeploy
script in package.json. We were just trying to reuse the exact same scripts during CI while having any interactive requirements turned off. We could have scripts with conditional logic or have separate scripts as @cool-egg-852 just suggested and all this would be fine. It just would mean that now we have two sources of truth as far as deployment scripts go. This is not a big issue, really just a small QoL change.white-balloon-205
What I’m suggesting is adding the global auto update as an opt in.Curious what you'd want that to look like? An env var perhaps?
prehistoric-account-60014
04/21/2020, 4:56 PMPULUMI_NON_INTERACTIVE=1
?white-balloon-205
cool-egg-852
04/21/2020, 5:00 PMPULUMI_ALWAYS_YES=1
prehistoric-account-60014
04/21/2020, 5:00 PMcool-egg-852
04/21/2020, 5:58 PM