Inspired by @SummitRoute's tracking changes of AWS IAM policies, I started similar project for @gcp
IAM roles:https://github.com/ecneladis/gcp_managed_roles …
-
Prikaži ovu nit
-
I noticed strange pattern of roles keep adding and removing parts of their policies.pic.twitter.com/jMsjmIOuZg
1 reply 1 proslijeđeni tweet 0 korisnika označava da im se sviđaPrikaži ovu nit -
For further analysis I downloaded json with list of all GCP roles 100 times in a very short period of time: - 71 different versions - all versions were valid json interpreted by jq - most common version had only 13 occurrencespic.twitter.com/sW3RNT7xHw
1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit -
Some examples of diffs between versions. Look like valid changes. No timestamps or something similar that would be expected to produce so many different json versions.pic.twitter.com/n93DPTqbBX
1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit -
Initially I thought that GCP managed roles are eventually consistent and I'm just catching the updates, but there's way too many versions in such a short period of tests. Any ideas what's happening here?
1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit
- Most likely error on my side? I always use same blank GCP project with same credentials. - Bug in GCP IAM? - Security feature of GCP API? (it's a feature!) - something else?
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.