incalculable-soccer-97284
12/27/2018, 7:23 PMpulumi update
is stuck in previewing update stage:
+- └─ aws:secretsmanager:SecretVersion integration_user_secret replace [diff: ~secretString]; completing deletion from previous update
-v doesn't seem to give me much, tips on how to probe into why it's hanging? I did a refresh and it completes successfully fwiw, but the freeze persists.incalculable-soccer-97284
12/27/2018, 7:24 PMgifted-island-55702
12/27/2018, 9:21 PMgifted-island-55702
12/27/2018, 9:25 PMgifted-island-55702
12/27/2018, 9:27 PMgifted-island-55702
12/27/2018, 9:32 PMgifted-island-55702
12/27/2018, 9:36 PMgifted-island-55702
12/27/2018, 9:37 PMgcloud
to modify a resource with an option that is not yet supported by terraform google provider. Is there a counterpart of local-exec provider in pulumi?gifted-island-55702
12/27/2018, 9:40 PMterraform state mv|rm
and/or terraform import
to achieve this. Is it supported in pulumi?gifted-island-55702
12/27/2018, 9:44 PMgifted-island-55702
12/27/2018, 9:46 PMgifted-island-55702
12/27/2018, 9:47 PMgifted-island-55702
12/27/2018, 9:54 PMgifted-island-55702
12/27/2018, 9:59 PMbusy-umbrella-36067
12/27/2018, 11:25 PMgifted-island-55702
12/27/2018, 11:55 PMgifted-island-55702
12/27/2018, 11:58 PMpulumi config set kubernetes:kubeconfig
but in my case I create a gke container and create kubeconfig that I want to use - is it possible to pass that kubeconfig to the default kubernetes provider instance or create my own instance of kubernetes provider and replace the default one?tall-librarian-49374
12/28/2018, 6:38 AMaz account get-access-token
every 30 minutes or so, otherwise login info is lost. As I understand, that's an issue on terraform side, but is there a workaround that pulumi could do? Like calling the command automatically.creamy-potato-29402
12/28/2018, 6:03 PMmost-pager-38056
12/28/2018, 7:25 PMJob.batch "api-migration-job-zdq5ov6o" is invalid: spec.template: Invalid value: [job spec]: field is immutable
I’ve tried to look at the @pulumi/kubernetes
source code, but seems like it’s generated automatically. In this case, how do we fix that? 🤔gifted-island-55702
12/28/2018, 10:49 PMwhite-balloon-205
Pulumi.yaml
file is a project. That project executes some program to do a deployment. See https://pulumi.io/reference/project.html.
There can be multiple instances of a single project deployed at a time. This is often the case for development/test/production, or for separate regions, etc. But some projects will just have a single instance, at least at some moment in time. Each instance of a project is a stack. See https://pulumi.io/reference/stack.html.
Today, the identity of a stack is <org>/<stack>
and the project is just metadata (tags) attached to it. That project metadata is used in the default rendering on the Projects
page at app.pulumi.com and to filter pulumi stack ls
CLI commands when in a project folder. But otherwise is just metadata. Only stacks exist.
We are moving to make the project part of the identity as <org>/<project>/<stack>
. As you note in the thread, this will make it natural to think of having a default
stack for a project in cases where you know you will only have one.gifted-island-55702
12/28/2018, 11:02 PMambitious-furniture-60362
12/29/2018, 3:49 PMpulumi/actions
and pulumi/pulumi
both are in dockerhub , looks like both are oficial https://hub.docker.com/r/pulumi/actions and https://hub.docker.com/r/pulumi/pulumi , no description into the images, i'm using them (just for poc) , and pulumi inside is a little bit old.busy-umbrella-36067
12/31/2018, 8:56 PMpulumi:pulumi:Stack XXXXXXXXX-images error: transport is closing
powerful-football-81694
01/01/2019, 1:40 PMconst resourceGroup =
new azure.core.ResourceGroup(
`retrospect-${envName}-infra`,
{
location: "westeurope"
}
);
Pulumi adds an auto-generated suffix to the name, like so:
retrospect-dev-infra5bf12d3a
Firstly, why is it doing this, and secondly, how can we override this behavior? We'd like to avoid that because we'll be encoding project and stack names into our resource names where necessary, so the random suffix just makes things more cluttered..faint-motherboard-95438
01/02/2019, 12:37 PMpg_hba.conf
but to create/delete users I need to run a command directly on the master pod.numerous-whale-2676
01/02/2019, 1:25 PMfaint-motherboard-95438
01/02/2019, 1:45 PMpulumi.Config
object constructor states that :
[…] For example, a bag whose name is pulumi:foo, with keys a, b, and c, is entirely separate from a bag whose name is pulumi:bar with the same simple key names.
Each key has a fully qualified names, such as pulumifooa, ..., and pulumibara, respectively.It gives as an example that a config could be named
pulumi:foo
which gives a possible fully qualified key pulumi:foo:a
.
Or if I try to define a config bag as such, I get an error :
error: invalid configuration key: could not parse foo:bar:ber as a configuration key (configuration keys should be of the form `<namespace>:<name>`)
It seems to refuse a :
in the Config
namecold-coat-35200
01/02/2019, 1:59 PMparameterGroupName
of an aws.elasticache.ReplicationGroup
is handled as an update, while it could contain "requires-reboot" type parameters,
like "databases" for redis, which will fail with:
updating urn:pulumi:dev::dliver::storage:elasticCache:redis$aws:elasticache/replicationGroup:ReplicationGroup::dlv-dev-rd-ch: error updating Elasticache Replication Group (dlv-dev-rd-ch): InvalidParameterValue: The parameter databases has a different value in the requested parameter group than the current parameter group. This parameter value cannot be changed for a cache cluster.
The "deleteBeforeReplace" option won't solve this, because we don't want any downtime, how can we handle these situations without manual intervention?
Currently, the only solution I can imagine to remove the "ReplicationGroup" from stack manually, create the new one with pulumi, then delete the old one manually from aws.