fix: GCP not recognizing access token #196
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue:
While running the package in a Google Cloud Function, an
AttributeError
was being raised about the access token. This was despite having setconfiguration.access_token
.Error log:
Right now I am remedying the issue with this helper function:
Which is obviously not ideal.
This resolves a bug similar to OpenAPITools/openapi-generator#7929 in the
openapi-generator
project which uses a similar fix as this one, found here OpenAPITools/openapi-generator#7469.Ensuring the
access_token
attribute is always initialized helps prevent this error from being raised. The only error from an emptyaccess_token
attribute should be one that comes back from the Asana API.