-
Notifications
You must be signed in to change notification settings - Fork 155
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.
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
Error when changing name of aws.secretsmanager.Secret() resource #2900
Comments
on Windows with Python 3.11 my requirements.txt has: |
@t0yv0 @VenelinMartinov is this the same as #2904? |
I've tried quickly if I can reproduce the problem here but unfortunately it does not reproduce for me. It tried variations of this program to generate update scenarios on Secret and replace scenarios on SecretVersion at pulumi-aws 6.0.2 and 6.8.0 but it did not panic for me. I'll continue with the repro in 2904. """An AWS Python Pulumi program"""
import pulumi
import pulumi_aws as aws
import pulumi_random as random
import json
pw = random.RandomPassword("mypassword",
length=12,
special=True,
override_special="!#$%&*()-_=+[]{}<>:?")
mysecret = aws.secretsmanager.Secret(
"mysecret",
opts=pulumi.ResourceOptions(delete_before_replace=True),
description="Master authentication information1",
)
aws.secretsmanager.SecretVersion(
"mysecretversion",
secret_id=mysecret.id,
secret_string=pulumi.Output.all(
username='myuserg',
password=pw.result,
host='myhost',
port=999,
engine='v12',
).apply(
lambda args: json.dumps(
{
"username": args["username"],
"password": args["password"],
"engine": args["engine"],
"host": args["host"],
"port": args["port"],
}
)
)) |
[Upstream v5.25.0 release notes](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.25.0) Fixes #2983, #2904, #2971, #2900 - [x] Rebuild eks.Cluster patches; upstream moved to AWS SDK v2 for Go, patches needed updates as well - [x] Fix pulumi/pulumi-terraform-bridge#1523 in the bridge - [x] Update bridge to include pulumi/pulumi-terraform-bridge#1521 and pulumi/pulumi-terraform-bridge#1520 fixes affecting P1s in pulumi-aws - [x] Build a Pulumi test for EKS Cluster add-on removal -> turns out the property is a no-op, not needed
While we could not reproduce this issue exactly, an issue with a very similar-looking stack trace got fixed in v6.9.0. Please open another issue if this surfaces again. |
Hi,
I generate a random password with
and save it in AWS Secrets Manager
Working with secrecretsmanager seems problematic. I get errors such as this one when I want to update the secret.
I am not certain if this is the right workflow for creating and storing passwords in Pulumi. I save the password in Secrets Manager so that my app can retrieve it from there to access the DB. (I create another non-master db role too. The workflow is the same above.)
What is the right/recommended workflow in Pulumi Python to create and save passwords when creating infra for use in app code?
Slack Message
The text was updated successfully, but these errors were encountered: