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.

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

The launchdarkly_project resource key length requirement does not match existing resources. #175

Closed
scuba10steve opened this issue Aug 10, 2023 · 4 comments

Comments

@scuba10steve
Copy link

scuba10steve commented Aug 10, 2023

When importing an existing project into a new Terraform repo, and then subsequently running a plan the provider responds back wtih an error Error: expected length of key to be in the range (1 - 20), got <redacted>. I've ommitted the actual key, but the length is 26 characters as it exists in the SaaS.

For reference the code here: https://github.com/launchdarkly/terraform-provider-launchdarkly/blob/main/launchdarkly/resource_launchdarkly_project.go#L73 is seeming to be inconsistent with existing projects, is this something that could be adjusted?

Also, just to double check, I created a project within the SaaS and was able to create one with a key length longer than 20 characters:

image

@ldhenry
Copy link
Collaborator

ldhenry commented Aug 10, 2023

He @scuba10steve, thanks for bringing this to our attention. We'll work on getting that updated in the next release. I'll let you know when it's available.

Thanks,
Henry

@scuba10steve
Copy link
Author

@ldhenry I'd be happy to provide a PR, but I don't know what length requirement makes sense, or if it should just be removed entirely.

Also, appreciate the feedback!

@ldhenry
Copy link
Collaborator

ldhenry commented Aug 10, 2023

Hey @scuba10steve, we just released v.214.0 of the provider with a max key length of 100 chars. Thanks for bringing this to our attention.

I'm going to close this issue, but feel free to re-open it if it's still not working for you.

Thanks,
Henry

@ldhenry ldhenry closed this as completed Aug 10, 2023
@scuba10steve
Copy link
Author

@ldhenry Thanks for the quick turn around! That should be sufficient for my use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants