Alexander Kim
Alexander Kim
> > if you do bigger refactors that won't work as it might try to create the new resource which just has a different name from the point of view...
To chime in here, I would prefer not having `getStack()` be changed as all of our automation currently depends upon this as it is today. We have for example `Pulumi.development.yaml`,...
This is still really needed.
Also having the same issue. It's weird that `eslint` itself is not showing anything, but it fails when run with `lint-staged`.
In this case it's `vault` that uses the `vault` provider, but yes.
I don't think we should have to rename the project to be honest. It makes perfect sense to have the project name be the same. What I think would make...
So what you mean is that instead of `projectName:key: value` we'd just have `key`? If so, then I'm not sure if I like it either, as it makes it harder...
Bumping this. Curious, is this app dead?
It’s built in I believe. It’s part of the development panel.
That's really good to know. I thought we had tried multiple files before and it failed, but maybe not.