-
Notifications
You must be signed in to change notification settings - Fork 2
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
Cycle error when removing AWS Lambda functions #2992
Labels
bug
[type] A defect preventing use of the system as specified
debt
[type] A defect incurring continued engineering cost
infra
[subject] Project infrastructure like CI/CD, build and deployment scripts
no demo
[process] Not to be demonstrated at the end of the sprint
orange
[process] Done by the Azul team
Comments
#2991 would be a FIXME introduced by the above patch. |
This was referenced Apr 16, 2021
melainalegaspi
added
debt
[type] A defect incurring continued engineering cost
infra
[subject] Project infrastructure like CI/CD, build and deployment scripts
labels
Apr 16, 2021
melainalegaspi
added
the
bug
[type] A defect preventing use of the system as specified
label
Sep 30, 2021
Examine viability of hashicorp/terraform-provider-aws#11344 (comment) as a workaround. |
hannes-ucsc
added a commit
that referenced
this issue
Nov 30, 2022
76 tasks
hannes-ucsc
added a commit
that referenced
this issue
Nov 30, 2022
hannes-ucsc
added a commit
that referenced
this issue
Nov 30, 2022
hannes-ucsc
added a commit
that referenced
this issue
Nov 30, 2022
dsotirho-ucsc
pushed a commit
that referenced
this issue
Dec 1, 2022
hannes-ucsc
added a commit
that referenced
this issue
Dec 1, 2022
hannes-ucsc
added a commit
that referenced
this issue
Dec 1, 2022
hannes-ucsc
added a commit
that referenced
this issue
Dec 2, 2022
dsotirho-ucsc
added a commit
that referenced
this issue
Dec 2, 2022
14 tasks
hannes-ucsc
added
the
no demo
[process] Not to be demonstrated at the end of the sprint
label
Dec 19, 2022
hannes-ucsc
added a commit
that referenced
this issue
Feb 9, 2023
#2992 made the stage an explicit resource, so that we can now refer to its `.arn` attribute.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
[type] A defect preventing use of the system as specified
debt
[type] A defect incurring continued engineering cost
infra
[subject] Project infrastructure like CI/CD, build and deployment scripts
no demo
[process] Not to be demonstrated at the end of the sprint
orange
[process] Done by the Azul team
https:/DataBiosphere/azul/pull/2969/files#r614245068
which is a manifestation of
hashicorp/terraform-provider-aws#11344
and despite my best efforts to follow the best practices
hashicorp/terraform-provider-aws#11344 (comment)
I wasn't able to fix. Here's what I tried:
still getting
during
terraform apply
against a deployment that's on the base commit of #2969 (064f2c1 on develop) with the PR branch checked out and the above patch applied. The same happens if I apply the patch to the base commit, then deploy (which succeeds), then switch to the PR branch and try to deploy again.There are some other changes mixed in, most prominently a fix for #1951 which we may fix before this one, so expect conflicts when applying the patch above.
The text was updated successfully, but these errors were encountered: