Sharing something I've been working on lately: an AWS IAM Language Server (and VSCode extension). Use it with any editor that supports LSP

It can emit diagnostics for invalid actions, messed up regions/account ids, duplicate sids, etc. It also gives you completion for actions, arns, condition operators, context keys, etc

It also supports policies defined in any YAML, JSON, or Terraform/OpenTofu file, at any nested level, so your policies defined within a CloudFormation resource will be picked up

Check out the repo for more, feel free to open an issue if you have issues: https://github.com/mbarneyjr/aws-iam-language-server

If you use vscode you can get the extension here: https://marketplace.visualstudio.com/items?itemName=MichaelB...

Demo video: https://x.com/mbarneyjr/status/2039329871843729809

I'm consistently hitting weird bugs with opencode, like escape codes not being handled correctly so the tui output looks awful, or it hanging on the first startup. Maybe after they migrate to opentui it'll be better

I do like the model selection with opencode though

JSDoc provides the exact same level of type safety as TypeScript, because the TypeScript Language Server/CLI themselves are what does the type checking. Using JSDoc removes the need to transpile your code before executing it. You still want to type-check your code (with a `tsc --noEmit` or similar) in CI, just like you'd run unit tests/a linter/etc.

Yes, that's my point. JSDoc isn't an alternative to TypeScript if you want your types to actually be checked.

In other words: this product is employing a pricing strategy that is overwhelmingly common in our industry (because it works).

And the industry is sick of it...? At least some vocal minority

Why strange? That was the first thing that came to mind when I read “sso” as part of the “enterprise’ offering, and was not surprised to see that someone else linked the sso tax website

You're right. I misread the original post and also managed to do a double fail and misunderstand the SSO Wall of Shame as well. Sorry, mbarneyme!

I think they mean "deterministic," not "immutable"

Yeah on further reflection maybe the "immutable" part of this is that I never use the Spotify UI to modify my playlist - it only gets changed during terraform apply phases, which may change the playlist in random ways on each re-apply.

Do you have those commands handy by chance? :D

Sure thing https://gist.github.com/erinok/0247c134a57acdb2e2daafdf1d77a...

It's a handful of commands because git-cam and git-wip referenced other little utility scripts, so hopefully I got them all. Probably it would be easy to rewrite to be standalone.

I'm on a mac, and I have ripgrep installed as "rg". Ymmv, glhf :-)

So:

"git cam" commits everything with message "nt"

"git wip" undoes all the nt commits but leaves the results staged, ready to be commited as a single properly worded commit (or play w/ what's staged and do as several commits)

It's usually something like:

    git status && git add -A git commit -m "checkpoint" --no-verify

I include `git status` so I can see what's being committed. `--no-verify` is used to skip any pre-commit hooks.

You can use `-v` on the add to see what it’s doing instead of the extra status