Use GCP selflink for tracking instances throughout #8
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.
When the compute API is first queried, the self link is used to form a resource ID that is put in the cache. After formatting, that looks like
but when creation events are received, the resource name uses the project ID instead of the number, which looks like
This leads to two types of resource IDs being stored in the cache. To fix this, compute resource IDs are stored in the form
which is formed from the self link.
Additionally, preemption events do not contain a self link, but the format of the resource ID matches what we stored in the cache.
This also fixes a small bug where an instance would be tracked even if parsing the pubsub message failed