aws_ssm_parameter resource does not have a overwrite option

[FransUrbo]

I'm trying to update/replace a Parameter Store value, but TF gives ParameterAlreadyExists.

Terraform Version

0.9.8

Affected Resource(s)

Please list the resources as a list, for example:

• aws_ssm_parameter

[FransUrbo]

I notice after I've deleted the param, run terraform apply and then ran terraform apply again some time later, that it can't detect that the parameter already exists!

So a better option (because I'm encrypting the parameter with a KMS key and I'm not sure TF can get the param, decrypt it with the key - how would it know WHICH key?? - and then check if it differs from what is in the state or the value option) might be to simply try see if the param already exists, and then ignore it (as in, not to create one).

[FransUrbo]

Another issue:

If the name value is changed (not sure if it's related to the param also been deleted), I get:

[ERROR] SSM Parameter XXX is invalid

Not sure if this is related to the original issue. If not, I'll open a new issue about that.

To get around that (since the param is deleted from the AWS Console), I simply removed it from the state and rerun apply.

[stack72]

@FransUrbo if possible, can you try and recreate that issue and then open an alternative about that?

[FransUrbo]

Ok, no worries!

Regarding the "can't detect already exists" above. This MIGHT be because I had the same resource name (but different name value) in several modules.

As in:

resource "aws_ssm_parameter" "hiera-private" {
    [...]
}

in all my modules. Prefixing the resource name, seems to have solved the "recreation issue"...

[FransUrbo]

PS. Please back port to 0.9 if possible!

[stack72]

Hi @FransUrbo

there will be no further releases of the 0.9 services I'm afraid

Paul

[FransUrbo]

Ok, bummer :(. So 0.10 is starting to be ok? Last I saw it was just a beta release... ?

[stack72]

@FransUrbo it was the first release in the major version series - it will take a few betas before we GA it

[FransUrbo]

If that's so, I'd very much like you to continue supporting 0.9. I'm not ready (i.e., brave/stupid enough), to hand my whole production environment to beta code!

[stack72]

Sorry, we are only making critical big fixes to 0.9.x series. Ann development effort is focused on 0.10 series now It will be ready for GA in a few weeks Paul

…

On Thu, 29 Jun 2017 at 23:05, Turbo Fredriksson ***@***.***> wrote: If that's so, I'd very much like you to continue supporting 0.9. I'm not ready (i.e., brave/stupid enough), to hand my whole production environment to beta code! — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1004 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAN578yREtXGORDSheplZ19LPXCbqNvoks5sJANugaJpZM4OJHDk> .

[FransUrbo]

That's kind'a what I meant by "support 0.9". I did NOT mean to add features etc into it so we're in full agreement there. However, we might have a slight disagreement on the word critical :).

This one does not comply to that IMO, just to make things clear :D.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!