Describe the bug
We discovered that the latest run with the config manager no longer pushes AWS Credentials. It worked on a previous version of the tool.

Has there been any change related to AWS Credentials?

Describe the bug
After adding the source and destination tenant and extracting all 4 configurations, an attempt to migrate using the migrate option failed

To Reproduce
Steps to reproduce the behavior:

1. Go to Extract files
2. Click on all 4 extract config buttons
3. Scroll down to migration button and click it
4. See error (on screenshot below)

Expected behavior
Successful config migration

Screenshots

Desktop (please complete the following information):

• OS: Windows 11 as VM on MAC using Parallels
• Browser Chrome

I have been attempting to run this project in a docker container and with only a little effort it is mostly working.

However, I'm at the point where I'm hitting the react-frontend and it, in turn, hits the backend and according to the JS console, it is getting a net::ERR_EMPTY_RESPONSE from the backend when the frontend is trying to hit:

• execution_options
• tenant_list
• entity_filter

I discovered that from cloning the repo I did not get the data/options dirs and files that I had in the release package (or weren't getting created) so I made sure they were present and could see non-empty responses from the backend calls. This, however, was still not the issue. From within the container I can curl the backend and get an expected response.

I thought CORS might be the culprit but the CORS policies are very open.

I'm not sure what else to try but I would really like to find a solution here.

If there is an issue with connectivity or a problem with the token the UI page gets stuck trying over and over. Even hitting OK doesn't make the window with error go away. Eventually you can get it past it. But if you need to Add a Proxy or change URL it get's stuck testing over and over. I would like to see the test connection option come back, or at least after initial test a re-try button. Otherwise you get stuck in the loop of it auto testing.

Describe the bug
When I try running the step for "Plan all and review" it seems the tool suddenly stops. I can see in the console the following line is logged:
"127.0.0.1 - - [11/Jan/2024 14:55:25] "POST /terraform_history_configs?tenant_key_main=0&tenant_key_target=1 HTTP/1.1" 200 -
The command cd /home/stian/src/dnb/test-dt-config-mgr/data/work/0-1/terraform/config
terraform plan -lock=false -parallelism=10 -out=./2024-01-11_14-55-25_complete.plan >NUL > /home/stian/src/dnb/test-dt-config-mgr/data/work/0-1/terraform/history/complete/2024-01-11_14-55-25/2024-01-11_14-55-25_plan_all.log 2>&1 failed with error code 1
Deleting old overall directory: /home/stian/src/dnb/test-dt-config-mgr/data/work/0-1/overall"

Out of curiosity I tried running the command, manually and I see multiple errors like:
"╷
│ Error: Unsupported block type
│
│ on modules/aws_credentials/AWS-CB-Migration-Dev_REGIONS_eu-west-1.aws_credentials.tf line 10, in resource "dynatrace_aws_credentials" "AWS-CB-Migration-Dev_REGIONS_eu-west-1":
│ 10: lifecycle {
│
│ Blocks of type "lifecycle" are not expected here.
╵
"

Screenshots

Desktop (please complete the following information):

• OS: WSL Ubuntu 20.04
• Browser: Edge (chromium)
• Version 1.1.0

Describe the bug
While terraform apply we get an error
FileNotFoundError: [WinError 2] system can't find specified file: 'C:/Users/myuser/bin/data/work/0-1/overall/activegate_updates\ENVIRONMENT_ACTIVE_GATE-000000xxxx.txt'
To Reproduce
Steps to reproduce the behavior:

• Plan All
• push all configuration

Expected behavior
No error on logs

Screenshots

Desktop (please complete the following information):

• OS: windows
• Browser Chrome
• Version: Config Manager 1.4.3

Hi

I am running the exe file from the URL https://github.com/Dynatrace/Dynatrace-Config-Manager/releases/tag/v1.4.14. I am running into following issue..

 ERROR HTTP Request failed with Error: Get "[https://XXXXXX.live.dynatrace.com/api/v2/entityTypes?pageSize=500":](https://lac49780.live.dynatrace.com/api/v2/entityTypes?pageSize=500%22:) read tcp 10.158.33.xxx:52710->52.2.227.xxx:443: wsarecv: An existing connection was forcibly closed by the remote host.

  Does anyone ran into this issue ?  

I am running VM image from MAC intel

Anything that you can help me with is greatly appreciated.

Hi!

I see from the output of the one-topology that it, in essence is monaco with some featureflags added (download entities among them)
Any plans on publishing this in the main monaco repo?

Describe the bug
We see that the management zone field is not being mapped during the creation of Alerting Profiles.

This seem to work just fine for other configuration items that have mapped MZ to it's settings. Such as Metric Events and Dashboards.

Is this trivial to fix?

Is your feature request related to a problem? Please describe.
Hi! Can you please bump the terraform provider to the newest version?

It would be good to have the option to map internal synthetic locations from source to target, something like the users csv but for locations, so you can assign synthetic http and browsers to a new locations.

Issue still seems to exist with 1.4.12. Neither updating an existing configuration nor adding a new configuration applies the management zone to the alert profile. Export shows the management zone with proper ID in SaaS but never gets applied to the configuration.