Viacheslav Vasilyev

another use-case This use-case covers optional headers to sign mentioned at https://docs.aws.amazon.com/general/latest/gr/sigv4-signed-request-examples.html ``` # Note: The request can include any headers; canonical_headers and # signed_headers lists those that you want...

another user-case https://github.com/kubernetes-sigs/aws-iam-authenticator#api-authorization-from-outside-a-cluster

would like to know it as well, I'm wondering whether a clean approach is even possible, the kubelet generated certificates will have 0600 permissions, so only the user running kubelet...

I just wanted to reuse the same certificates specifically issued for/by kubelet, but it seems I would need to have another pair of certificates for metrics-server

you have list of projects, commits should be attached to a project's repo ``` /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits ```

you've got iterator, just iterate over the output using for loop ``` for commit in bitBucket.projects[project['key']].repos[repo.get('slug')].commits('2020-03-03','2020-02-02').all(): print(commit) ```

looks like not hard to implement ``` /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests?state=MERGED ```

probably this is the only option ```bash VIRTUAL_ENV='C:\Users\xyz\Projects\abc\.venvwin' if ([ "$OSTYPE" = "cygwin" ] || [ "$OSTYPE" = "msys" ]) && $(command -v cygpath &> /dev/null) ; then VIRTUAL_ENV=$(cygpath -u...

support both with ```python self.props['Code'] = ((troposphere.awslambda.Code, str), True) ```

static routes? ``` $ cat /etc/syconfig/network-scripts/route-ens3 10.2.3.128/25 via 192.168.252.51 dev ens3 10.2.48.0/25 via 192.168.252.52 dev ens3 ```