-
Notifications
You must be signed in to change notification settings - Fork 26
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
Unexpected folder naming when providing s3 bucket as storage container #756
Comments
@tasdomas do you have availability to take a look? |
Hello, @LahiLuk! Probably long identifiers would be more adequate than short identifiers in this case. Unfortunately, when writing #687, user experience wasn't our topmost priority. Feel free to open a pull request replacing terraform-provider-iterative/task/aws/task.go Lines 57 to 59 in a0fb6be
terraform-provider-iterative/task/az/task.go Lines 47 to 49 in a0fb6be
terraform-provider-iterative/task/gcp/task.go Lines 48 to 50 in a0fb6be
|
I'm not entirely sure if this is a bug or a feature, but it would be good to know in order to be able to automate actions based on the expected output.
I'm using TPI and passing an AWS s3 bucket as the storage container, i.e.
Since I haven't specified any folder inside the bucket, I would expect that a folder with the task ID will be created, e.g.,
tpi-basically-fit-oryx-xjezxu77-5eudru0h
. However, what happens is that a folder named justxjezxu775eudru0h
is created, which is in contrast to all the other resources being named following the full task ID. Is this expected behavior?The text was updated successfully, but these errors were encountered: