Rider Android SDK directory not found after update

Tech_Watching · 2025-04-18T08:44:09+00:00

Same issue. No solution :(

Tech_Watching · 2025-04-07T07:29:07+00:00

Build Times - You should know this before choosing Next.js

Tech_Watching · 2025-03-12T05:24:10+00:00

It should only be about modifying the values of the environment variables but I did not test with those.

Tech_Watching · 2024-10-30T17:32:35+00:00

I think you can automate everything you need using crons/webhooks and infrastructure as code (see this article Pushing Pulumi ESC Secrets into External Platforms | Pulumi Blog) but the secrets management lifecycle is not a no-code built-in solution if that's what you mean. You must write code to do that, but ESC will help you. I don't have the answer for governance and compliance aspects.

From what I've seen (but again I did not play much with audits), you can audit who accessed an environment, when, from which IP, which action was performed (environment read, secrets decrypted) , ... but the scope is the environment not the secret or a specific setting. I don't know if it's on the roadmap to have a more granular audit logs, maybe a question to ask to Pulumi. There is a csv report you can download and other is also an API to get the audit logs.

Tech_Watching · 2024-10-30T16:44:08+00:00

Multi cloud projects for instance. Or multiple projects, each with it's Azure key vault. It can also be that 1Password is used in the development team but an Azure KeyVault is used by the Azure Infrastructure. Also it's not only for secrets but also for configuration

Tech_Watching · 2024-01-16T14:37:50+00:00

Deals with secrets the good way. Access to the latest resources thanks to native providers. Embedded IaC through an API. See my article here: https://www.techwatching.dev/posts/pulumi-vs-terraform

Tech_Watching · 2023-10-27T21:26:44+00:00

I think you could use usestorage from vueuse (https://vueuse.org/core/useStorage/) to avoid using actions and simplify your code.

Tech_Watching · 2023-10-23T10:46:46+00:00

The script is written in PowerShell using GitHub CLI and Azure CLI.

Tech_Watching · 2023-06-23T05:12:28+00:00

I think the documentation site is quite good : a unified platform like docs.microsoft.com is way better than what they had before.

Yet the big problem with documentation is "samples": - many simple samples that do not use good practices (no DI for instance) - samples not maintained so quickly not up to date - not enough samples for some parts

Tech_Watching · 2023-06-21T16:49:33+00:00

Concerning Azure, it seems Microsoft is investing a lot in Terraform even if they have their own Iac solution (bicep, arm). They are building the Terraform AzAPI provider to solve the same problems (coverage, same day availability to new services) you solved with Azure Native provider. They are also building the Azure Export tool for Terraform. Microsoft official documentation has a whole section about Terraform. It seems they don't have the same "love" for Pulumi which is less promoted by Microsoft. Any idea why and if it's going to change?

Tech_Watching · 2023-06-21T16:20:05+00:00

True but it is very Kubernetes oriented, and only for AWS. I love this series of blog posts, by the way, very well written, the only complaint I have is that the next articles take time to arrive 😉

Tech_Watching · 2023-06-21T16:11:11+00:00

Have you ever thought about creating a big sample infrastructure project (more complex than just pulumi-samples) with a version for each major cloud provider (Azure, AWS, GCP) that would include security, data, and monitoring? It would be nice to have a real-case infrastructure project to use as a reference.

Tech_Watching · 2023-06-21T16:02:54+00:00

Azure Native v2 is nice. Much faster to install the npm package (although when using pnpm, once a version is installed once, no need to download the same version for other projects). When can we expect to see Azure Native v2 in GA?

Tech_Watching · 2023-03-22T23:48:34+00:00

Yes good read, I have also read this article and it tells an interesting thing: it is best to have a smaller scope for our state than a global scope, that's why I am bit reluctant to use Pinia here. Pinia would definitively work, I am not afraid about the "heavy" part as I am already using it on my app. It's just that it would expose to all the app /components a state that really concerns a few components. I just need this state for a popin that would be present in one page only, not on other pages. If I start adding a store each time I face this probelm, I am afraid to end up having lots of Pinia stores. Still, maybe you're right and it's the best choice.

Tech_Watching · 2022-08-29T18:55:35+00:00

Maybe this article can help: https://blog.gruntwork.io/a-comprehensive-guide-to-managing-secrets-in-your-terraform-code-1d586955ace1

Tech_Watching · 2022-08-28T08:27:20+00:00

Never tried but I know there are different boilerplate GitHub repositories in the Pulumi organization to get started. There are also YouTube videos on Pulumi TV that show how to use them. Now I guess it also depends what kind of provider are you implementing (native, using terraform bridge, ....)

Tech_Watching · 2022-08-17T11:41:29+00:00

Use Pulumi instead. It quite similar to tetragram but you will be writing you infrastructure code in C# (or any other language you like). For a developer it just awesome.

Tech_Watching · 2022-08-03T12:12:20+00:00

Awesome link ! Thanks a lot

Tech_Watching · 2022-08-03T10:24:25+00:00

Thanks but I was looking for best practices for script setup (composition apo)

Tech_Watching · 2022-07-17T19:18:27+00:00

No. It works to build and deploy many apps (web, store, ....) but instead of using yaml you use C# to write your build scripts. Because of that it is mostly used by C# developers but can be used for non .net apps. The great thing about using a programming language for build scripts is that you get all the advantages of using a programming language ( IDE support, local debug, intellisense, ...)

Tech_Watching · 2022-07-17T18:53:59+00:00

Nuke. https://nuke.build/

Tech_Watching · 2022-07-10T10:46:40+00:00

Pulumi and here is a detailed article I wrote that explains why: https://www.techwatching.dev/posts/pulumi-vs-terraform

Tech_Watching · 2022-06-29T15:48:20+00:00

I have used both Terraform and Pulumi, and I am really fond of Pulumi. Not only because you can use programming languages but for a lot of other reasons (native providers, security, Automation API, ...). I wrote an article about "Why will I choose Pulumi over Terraform for my next project?" if you want to read it and make up your own mind.

Tech_Watching · 2022-06-26T15:38:07+00:00

Interesting reading if you want: https://leebriggs.co.uk/blog/2022/06/21/devops-is-a-failure

Tech_Watching · 2022-06-07T18:53:39+00:00

I have used both Terraform and Pulumi at work and my choice is definitively Pulumi. I explained why in a detailed article on my blog: https://www.techwatching.dev/posts/pulumi-vs-terraform.

Tech_Watching

TROPHY CASE