magodo
@manjeetsinghcodz You can do that via https://github.com/magodo/tfadd, which is used by `aztfy` under the hood.
@rtorato You can check out the readme: https://github.com/magodo/tfadd#usage. Once https://github.com/Azure/aztfy/pull/166 is merged, there would be first class subcommand for the single resource scenario.
@rtorato v0.6.0 is now released.
@koudaiii Awesome! Thank you!
@stemaMSFT I've made an AUR package for `aztfy`: https://aur.archlinux.org/packages/aztfy-bin, which serves for the Arch Linux.
Is there any update on this issue?
@katbyte Thank you for looking into this! The naming of the options and the wildcard pattern is inherited from https://github.com/mvdan/gogrep, where the spelling of the "-x", "-g" and "-v" verbs...
It seems adding a default plan modifier like proposed above seems extends the scope of plan modifier to non-computed attributes? https://github.com/hashicorp/terraform-plugin-framework/blob/52f814f49dabda31377650235a37266e0f607114/tfsdk/attribute.go#L101
@tmccombs In SDK v2, setting a default value for optional and non-computed attribute is allowed. It is weired to mark an optional attribute as computed only for being able to...
@tmccombs BTW, should the check above be modified to, as otherwise, it will always be resolved to `true`? ```go if val.IsKnown() && !val.IsNull() { return } ```