cdktn-cli: cdktn is fetching providers and re-initing stack on every deploy/diff

[nchowinf]

Expected Behavior

To avoid re-initializing the backend and pulling providers on every run, and to apply the changes directly.

Actual Behavior

tenant-staging  Initializing the backend...
tenant-staging  Initializing provider plugins...
                           - terraform.io/builtin/terraform is built in to OpenTofu
                           - Reusing previous version of hashicorp/aws from the dependency lock file
tenant-staging  - Using previously-installed hashicorp/aws v6.36.0
tenant-staging  OpenTofu has been successfully initialized!

                           You may now begin working with OpenTofu. Try running "tofu plan" to see
                           any changes that are required for your infrastructure. All OpenTofu commands
                           should now work.

                           If you ever set or change modules or backend configuration for OpenTofu,
                           rerun this command to reinitialize your working directory. If you forget, other
                           commands will detect it and remind you to do so if necessary.
tenant-staging  - Fetching hashicorp/aws 6.36.0 for linux_amd64...
tenant-staging  - Retrieved hashicorp/aws 6.36.0 for linux_amd64 (signed, key ID 0C0AF313E5FD9F80)
                           - Obtained hashicorp/aws checksums for linux_amd64; All checksums for this platform were already tracked in the lock file
tenant-staging  Success! OpenTofu has validated the lock file and found no need for changes.
tenant-staging  data.terraform_remote_state.cross-stack-reference-input-officesites-multitenant-distribution: Reading...
tenant-staging  data.terraform_remote_state.cross-stack-reference-input-officesites-mult

Steps to Reproduce

cdktn deploy --skip-synth --auto-approve '*'
cdktn diff

Versions

cdktn: 0.22.0
cdktn-cli: 0.22.0

Providers

No response

Gist

No response

Possible Solutions

No response

Workarounds

No response

Anything Else?

No response

References

No response

Help Wanted

• I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[so0k]

@nchowinf - thank you for this (and perhaps I have to update the BUG Issue template to capture this as part of opening an issue), but I'm curious if you saw the same behaviour in cdktf-cli and this is an old bug (not sure if there was an existing issue in the old repo as well?)

or if this is an issue we introduced when we renamed things and migrated to a new scope on npmjs?

EDIT: added to bug report templates #86

[jsteinich]

@nchowinf which OS are you running on?

I'm wondering if this is the same as hashicorp/terraform-cdk#3737.
If so, could you please try running terraform providers lock to see if anything changes?