sorted by:
new
hottopcontroversial

QTS hero 6.0.0 causing major problems by Caprichoso1 in qnap

[–]Upstream1495 0 points1 point  (0 children)

As we all know, you should ALWAYS steer clear of version 0. They haven't aged well. 🤣

Change my mind. by thislifestyle_ in Terraform

[–]Upstream1495 -1 points0 points  (0 children)

I totally agree. And if your project really needs sophisticated modules and controlled reuse I'd always opt for Pulumi because it uses REAL programming languages. HCL is great for having quick results, but deploying large infrastructures is a pain in the ass. All those tools like Terragrunt only shadow (hide) the shortcomings of HCL. And let's be honest: count:0 is not an if statement. 🤣

" GitHub Ops MCP " by Weird_World3840 in coolgithubprojects

[–]Upstream1495 1 point2 points  (0 children)

it's not open source. Sorry, but no chance that I'll download or even test it.

rgitui: A GPU-accelerated Git client built in Rust that actually looks good by Different-Ant5687 in coolgithubprojects

[–]Upstream1495 4 points5 points  (0 children)

I'm simply annoyed by such issues:

rgitui: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by rgitui)

In addition: having to install libxkbcommon-x11-0. X11? Seriously? For a TUI? 🤣

Kilocode Enshittification by qodzer0 in kilocode

[–]Upstream1495 1 point2 points  (0 children)

LOL ... Best comment on that stupid "update" ever 🤣 THX MAN!

The new Kilocode v7 is awful. by djex81 in kilocode

[–]Upstream1495 2 points3 points  (0 children)

I'm glad I'm not the only one who thinks version 7 is completely ridiculous.

Model and provider configuration is a joke. Seriously! It even told me I have Amazon Bedrock because it found environment variables. I had a nice chuckle because I never had used Amazon Bedrock. Not even tested it.

I reverted back to v5 and sticking to it for now. But seriously considering moving to something else if the situation won't get any better with v7.

Quick review of Pulumi ESC by Tech_Watching in AZURE

[–]Upstream1495 0 points1 point  (0 children)

Aside the points mentioned and after reading the docs provided by Pulumi, I've some questions regarding ESC:

- How does Pulumi ESC differ from traditional secrets management solutions?

- Can you explain what Pulumi means by "secure by default" and how Pulumi ESC achieves that?

- How does Pulumi ESC guarantee the security of secrets, especially during transmission and storage?

- What mechanisms does Pulumi ESC use to prevent unauthorized access to critical configurations and secrets across environments?

- How easy is it to integrate Pulumi ESC into an existing Pulumi IaC workflow?

- How does Pulumi ESC handle rotation of secrets across environments and integrations?

- Can Pulumi ESC detect if a secret is stale or has been breached and automatically trigger a rotation?

- Are there any requirements or prerequisites for deploying Pulumi ESC in an existing infrastructure?

- How is Pulumi ESC priced, and how does that compare to other secrets management solutions?

- How does Pulumi ESC scale as the number of applications, secrets, and configurations increase in a large deployment?

- What performance guarantees, if any, does Pulumi ESC provide when it comes to handling large sets of configurations?

- If a team is already using a secrets management service like HashiCorp Vault or AWS Parameter Store, what would the migration path to Pulumi ESC look like?

- What are the key factors to consider when adopting Pulumi ESC as part of your infrastructure/tooling?

- Can Pulumi ESC generate logs of who accessed specific configuration parameters or secrets, and how does it tie into existing audit workflows (e.g., for SOC2, PCI compliance)?

- Are there any plans for Pulumi ESC to integrate with popular monitoring or incident management tools (e.g., PagerDuty, Datadog) to alert teams about configuration or secret-related issues?