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

Import errors on scripts/provision_credentials.py #2228

Closed
amarjandu opened this issue Sep 3, 2020 · 5 comments
Closed

Import errors on scripts/provision_credentials.py #2228

amarjandu opened this issue Sep 3, 2020 · 5 comments
Assignees
Labels
debt [type] A defect incurring continued engineering cost demoed [process] Successfully demonstrated to team infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team spike:1 [process] Spike estimate of one point

Comments

@amarjandu
Copy link
Contributor

amarjandu commented Sep 3, 2020

Import errors when trying to destroy google_service_account using Terraform
see error in:
https://gitlab.dev.singlecell.gi.ucsc.edu/snippets/7

Note that the service account that was being used was still destroyed as requested.

@amarjandu amarjandu added orange [process] Done by the Azul team debt [type] A defect incurring continued engineering cost infra [subject] Project infrastructure like CI/CD, build and deployment scripts labels Sep 3, 2020
@amarjandu
Copy link
Contributor Author

@hannes-ucsc 'ideally errors would not be present, if not, explain that they are benign either in the process output, or within the README.md'

@amarjandu amarjandu added the spike:1 [process] Spike estimate of one point label Sep 3, 2020
@amarjandu
Copy link
Contributor Author

Note that in the attached log there terraform command that was run was
terraform destroy -target=google_service_account.service_account
while from the develop branch the command is
terraform destroy -target=google_service_account.indexer
The error is the same regardless of the changes to the resource name.

@melainalegaspi melainalegaspi removed the spike:1 [process] Spike estimate of one point label Oct 2, 2020
@melainalegaspi
Copy link

@hannes-ucsc :"Don't know why this was spiked. To be triaged."

@amarjandu
Copy link
Contributor Author

amarjandu commented Oct 2, 2020

@hannes-ucsc this was spiked to confirm that the errors were in fact benign.

@melainalegaspi melainalegaspi added the spike:1 [process] Spike estimate of one point label Oct 2, 2020
@jessebrennan
Copy link
Contributor

The printed stack traces are benign. The warning that precedes them explains the issue. It's possible to filter them out googleapis/google-api-python-client#299 (comment) which is what I'll do.

@melainalegaspi melainalegaspi added the demoed [process] Successfully demonstrated to team label Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debt [type] A defect incurring continued engineering cost demoed [process] Successfully demonstrated to team infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team spike:1 [process] Spike estimate of one point
Projects
None yet
Development

No branches or pull requests

4 participants