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
Invalid creationTimestamp when creating a regional network endpoint group with the beta api #611
Comments
I was able to workaround this by using the classic GCP provider and importing a manually created NEG, so not a pressing issue, but I did see the creationTimestamp issue there as well. |
@sudermanjr thanks for opening the issue! In your call to create the regional NEG, you want to replace the apiGW.ID() call with That said, investigating this issue helped identify a problem with how we were storing ids for some resources like Gateway - where the URL tracking the creation operation was being misconstrued as the identifier to retrieve the resource. The change in #615 fixes this. I am providing an example in typescript of creating a function backend, api, api config, Gateway and NEG in typescript as reference which seems to work after the fix in #615
|
What happened?
Got the following error message:
Steps to reproduce
Expected Behavior
The NEG gets created
Actual Behavior
The error message from above.
Versions used
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: