You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An integration will be started, but will not finish and remain in the pending state. Generating a second integration via the portal and providing AWS_ACCESS_KEY and AWS_SECRET_KEY via the portal will finish the process and result in a finished integration.
Importing this successful integration into state will actually show both styles of credentials: credentials.key and credentials.role.
The pending integration will not return a credentials.role, nor does the provider allow for passing of both credentials.key and credentials.role.
On inspection, the generated mondoo_integration_aws will NOT have credentials.role in the statefile, which are likely returned via AWS itself.
Follow the example posted on the registry page, and link an integration to a space. On terraform apply, you will successfully build the space and create a pending AWS integration.
To compare to a functioning integration, create a second AWS integration by hand, generate a second mondoo_integation_aws resource:
this will bring this into your statefile for cross compares. You can then open this up in terraform console for exploration:
terraform init
terraform console
$ mondoo_integration_aws.import
# You'll see an output that includes role_arn
$ mondoo_integration_aws.original
# You'll see an output that does NOT include role_arn - This is the pending state integration.
Expected Behavior:
Generation of the AWS Integration that successfully exits the pending state and arrives at the "success" state.
Desktop:
OSX
Terraform Provider Version: 0.18.0
Terraform Version: 1.9.8
The text was updated successfully, but these errors were encountered:
Bug:
When generating a new mondoo AWS Integration via terraform, such as:
An integration will be started, but will not finish and remain in the pending state. Generating a second integration via the portal and providing AWS_ACCESS_KEY and AWS_SECRET_KEY via the portal will finish the process and result in a finished integration.
Importing this successful integration into state will actually show both styles of credentials: credentials.key and credentials.role.
The pending integration will not return a credentials.role, nor does the provider allow for passing of both credentials.key and credentials.role.
On inspection, the generated mondoo_integration_aws will NOT have credentials.role in the statefile, which are likely returned via AWS itself.
Reproducing:
https://registry.terraform.io/providers/mondoohq/mondoo/latest/docs/resources/integration_aws
Follow the example posted on the registry page, and link an integration to a space. On terraform apply, you will successfully build the space and create a pending AWS integration.
To compare to a functioning integration, create a second AWS integration by hand, generate a second mondoo_integation_aws resource:
and then run:
this will bring this into your statefile for cross compares. You can then open this up in terraform console for exploration:
Expected Behavior:
Desktop:
The text was updated successfully, but these errors were encountered: