You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From looking at your code, I could see you intended to cache tokens for the lifetime of the plugin.
But it seems that, despite the gradle daemon staying around, the plugin instance does not.
To test the hypothesis, I ran the same command twice, and expected the second one to not output anything (ie. no GetAuthorization, because the token from the first one is not expired yet).
The intention of the plugin is just to reuse the token during the life of a command. Reuse the token in multiple references to the same repository.
I my experience using codeartifact, there is no problem in creating new tokens for each command execution (apart from the time taken to perform authentication).
We don't know how to reuse this information via Gradle daemon. Do you have experience?
We don't know how to reuse this information via Gradle daemon. Do you have experience?
Unfortunately no. In the past I myself would export a code artifact token as environment variable through direnv's .envrc, so as to only generate one per shell lifetime, and I would start the IDE from that shell.
I'm indeed worried about potential request throttling. Time will tell.
From looking at your code, I could see you intended to cache tokens for the lifetime of the plugin.
But it seems that, despite the gradle daemon staying around, the plugin instance does not.
To test the hypothesis, I ran the same command twice, and expected the second one to not output anything (ie. no GetAuthorization, because the token from the first one is not expired yet).
The text was updated successfully, but these errors were encountered: