Skip to content
Discussion options

You must be logged in to vote

This is expected. The container itself is what is currently being leased with the app lease feature. Because there hadn't been a need to store any information in our initial iteration of this feature, it wasn't necessary to actually add a blob to the container, just use it to represent the lease.

In an upcoming update to the app lease feature, there will be a blob inside that container that stores information about which app currently owns the lease. This update is really cool because it will allow apps to steal the app lease using a new http api and will also let apps automatically reset themselves to the waiting stage, trying to acquire the app lease for failure situations again. Previo…

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by amdeel
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants