carlpett
Repos
107
Followers
52
Following
2

A Terraform provider for reading Mozilla sops files

357
44

Prometheus exporter for Windows machines

1968
521

Convert a BIND zonefile to Terraform resource definitions for AWS Route53

52
7

A Prometheus exporter for extracting metrics from streaming sources of text

29
11

Prometheus exporter for Zookeeper

93
38

A TeamCity plugin for running .NET xUnit tests

46
13

Events

closes issue #88

Closes issue #88: https://github.com/carlpett/terraform-provider-sops/issues/88

Merge pull request #93 from fardarter/patch-1

closes issue #88

Created at 3 weeks ago
pull request closed
closes issue #88

Closes issue #88: https://github.com/carlpett/terraform-provider-sops/issues/88

Created at 3 weeks ago
Decrypting binaries

Hi @adamhealthhero, Somehow I missed this when it was opened, sorry about that.

Looking at this now, though, I'm unable to reproduce your results. There's also a unit test checking this (although not specifically writing it to local_file). Can you still reproduce this?

Created at 3 weeks ago
pull request closed
Workaround for sops #555

REF: https://github.com/mozilla/sops/issues/555

I need something like this because we apply terraform in our CD pipelines. Humans need to assume a role on their machine to use sops. CI/CD doesn't because those machines have access via AWS Instance Profiles.

I don't know a better solution to this problem. It would be nice to rely on structured data manipulation. Unfortunately the content must be munged before passing to the sops library. If the role config is present then sops will try to assume that role.

I'm not sure if this PR should be merged. I'm opening for feedback in search of a better solution.

Created at 3 weeks ago
Workaround for sops #555

Hey, Since this approach won't be merged, I'll close the PR. Thanks for the suggestion, though!

Created at 3 weeks ago

Fix expiry-key and token-key

Created at 1 month ago

Fix expiry-key and token-key

Created at 1 month ago

Fix expiry-key and token-key

Created at 1 month ago

Use gke-gcloud-auth-plugin

Created at 1 month ago
"We shouldn't be creating another debugger instance for this window"

I've just installed this extension, and tried following along with the instructions. However, in the second step where I do "Debugger: Install adapter", there's no feedback. Checking the Console, the message "We shouldn't be creating another debugger instance for this window" is logged. Is there a problem running the extension with multiple sublime windows open? I typically have 10 or so windows open on different projects.

If this is supposed to work, are there any hints on how to find the issue?

Running on build 4126, on Linux 5.16.19-200.fc35.x86_64. Let me know if there are other specifics that would be helpful!

Created at 1 month ago
"We shouldn't be creating another debugger instance for this window"

Ah. Yes, a restart fixed it :+1:

Created at 1 month ago
"We shouldn't be creating another debugger instance for this window"

I've just installed this extension, and tried following along with the instructions. However, in the second step where I do "Debugger: Install adapter", there's no feedback. Checking the Console, the message "We shouldn't be creating another debugger instance for this window" is logged. Is there a problem running the extension with multiple sublime windows open? I typically have 10 or so windows open on different projects.

If this is supposed to work, are there any hints on how to find the issue?

Running on build 4126, on Linux 5.16.19-200.fc35.x86_64. Let me know if there are other specifics that would be helpful!

Created at 1 month ago
IgnoreIncomingRequestHook ignored?

What happened?

It seems the result of ignoreIncomingRequestHook is, ironically, ignored.

Steps to Reproduce

new HttpInstrumentation({
  ignoreIncomingRequestHook: (req) => {
    if (req.method === 'OPTIONS') {
      return false
    }
    return true
  }
})

Expected Result

OPTIONS requests do not generate traces

Actual Result

OPTIONS requests do generate traces

Additional Details

Looking at the compiled js, it seems these lines: https://github.com/open-telemetry/opentelemetry-js/blob/a5abee69119cc41d9d34f6beb5c1826eef1ac0dd/experimental/packages/opentelemetry-instrumentation-http/src/http.ts#L382-L403 ... gets compiled into this:

            if (utils.isIgnored(pathname, instrumentation._getConfig().ignoreIncomingPaths, (e) => instrumentation._diag.error('caught ignoreIncomingPaths error: ', e)) ||
                (0, instrumentation_1.safeExecuteInTheMiddle)(() => { var _a, _b; return (_b = (_a = instrumentation._getConfig()).ignoreIncomingRequestHook) === null || _b === void 0 ? void 0 : _b.call(_a, request); }, (e) => {
                    if (e != null) {
                        instrumentation._diag.error('caught ignoreIncomingRequestHook error: ', e);
                    }
                }, true)) {
                return api_1.context.with((0, core_1.suppressTracing)(api_1.context.active()), () => {
                    console.log('???')
                    api_1.context.bind(api_1.context.active(), request);
                    api_1.context.bind(api_1.context.active(), response);
                    return original.apply(this, [event, ...args]);
                });
            }

Specifically, the return (_b = (_a = ... does not appear to return the actual result of the hook. If I split the assignment and return, everything works as expected.

OpenTelemetry Setup Code

No response

package.json

"@opentelemetry/api": "^1.1.0",
    "@opentelemetry/instrumentation-express": "^0.30.0",
    "@opentelemetry/instrumentation-http": "^0.32.0",
    "@opentelemetry/instrumentation-pg": "^0.30.0",

Relevant log output

No response

Created at 2 months ago
IgnoreIncomingRequestHook ignored?

Oh my. Not sure how I got that mixed up 🤦 Sorry for the noise!

Created at 2 months ago
IgnoreIncomingRequestHook ignored?

What happened?

It seems the result of ignoreIncomingRequestHook is, ironically, ignored.

Steps to Reproduce

new HttpInstrumentation({
  ignoreIncomingRequestHook: (req) => {
    if (req.method === 'OPTIONS') {
      return false
    }
    return true
  }
})

Expected Result

OPTIONS requests do not generate traces

Actual Result

OPTIONS requests do generate traces

Additional Details

Looking at the compiled js, it seems these lines: https://github.com/open-telemetry/opentelemetry-js/blob/a5abee69119cc41d9d34f6beb5c1826eef1ac0dd/experimental/packages/opentelemetry-instrumentation-http/src/http.ts#L382-L403 ... gets compiled into this:

            if (utils.isIgnored(pathname, instrumentation._getConfig().ignoreIncomingPaths, (e) => instrumentation._diag.error('caught ignoreIncomingPaths error: ', e)) ||
                (0, instrumentation_1.safeExecuteInTheMiddle)(() => { var _a, _b; return (_b = (_a = instrumentation._getConfig()).ignoreIncomingRequestHook) === null || _b === void 0 ? void 0 : _b.call(_a, request); }, (e) => {
                    if (e != null) {
                        instrumentation._diag.error('caught ignoreIncomingRequestHook error: ', e);
                    }
                }, true)) {
                return api_1.context.with((0, core_1.suppressTracing)(api_1.context.active()), () => {
                    console.log('???')
                    api_1.context.bind(api_1.context.active(), request);
                    api_1.context.bind(api_1.context.active(), response);
                    return original.apply(this, [event, ...args]);
                });
            }

Specifically, the return (_b = (_a = ... does not appear to return the actual result of the hook. If I split the assignment and return, everything works as expected.

OpenTelemetry Setup Code

No response

package.json

"@opentelemetry/api": "^1.1.0",
    "@opentelemetry/instrumentation-express": "^0.30.0",
    "@opentelemetry/instrumentation-http": "^0.32.0",
    "@opentelemetry/instrumentation-pg": "^0.30.0",

Relevant log output

No response

Created at 2 months ago
Invalid index error using terraform import

Thanks for the update, and happy that it works :)

Created at 2 months ago
Invalid index error using terraform import

Hi @BroderPeters, I would have expected this to work, and am unsure why it wouldn't. I can't easily reproduce it, though. Could you try running the import with environment TF_LOG=1 and share relevant log lines? My best guess is that the data source isn't initialized properly during the import, but it's hard to know exactly why.

Created at 2 months ago
Intermittent timeout on connects

It's... Quite a lot more that I expected! Or at least looking at the New connection for "<instance>" log from the proxy, which should be a decent metric for this? Not near 3k/minute, but it's around ~1-2/second, 140k total over the last 24h. Out of those we have 7-10 failures per day.

Created at 2 months ago
opened issue
x/website: Fuzzing documentation image has transparent background, works poorly with dark mode

The fuzzing page, https://tip.golang.org/security/fuzz/, has an image describing different components involved. It however has a transparent background, and with the page supporting dark mode, the image gets very tricky to read: image

I'm not sure if having a opaque white background would be problematic, but that seems to be the easiest solution.

Created at 2 months ago
Intermittent timeout on connects

@enocom Yes, sorry for not mentioning that, it's all IAM auth.

Thanks for checking with the team! Let me know if we can provide any other info!

Created at 2 months ago
Intermittent timeout on connects

Bug Description

A couple of times per day, we get a odd timeout error logged in CloudSQL when connecting to instances, and a "authentication failed" error message on the client:

2022-09-02 14:08:13.336 UTC [488068]: [2-1] db=[dbname],user=[serviceaccount-id]@[project].iam DETAIL:  Deadline Exceeded
Connection matched pg_hba.conf line 21: "local   all           +cloudsqliamserviceaccount         cloudsql-iam-svc-acct"
connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL:  Cloud SQL IAM service account authentication failed for user [serviceaccount-id]@[project].iam

How to reproduce

Very unclear. Our application currently uses a crash+restart as a retry mechanism, and connecting works when coming back. Existing open connections appear to work while the new one fails. There is no clear indication in metrics that there is a load related issue.

We're seeing this across several applications, different service accounts and cloud sql instances, however, so it doesn't appear to be related to a single "bad" thing.

Environment

  1. OS type and version: GKE COS v1.21.13-gke.900
  2. Cloud SQL Proxy version (./cloud-sql-proxy --version): 1.30.1
Created at 2 months ago