Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keystrokes.credential.vault_id in dynatrace_browser_monitor fails validation #259

Closed
coolmancgfs opened this issue May 24, 2023 · 2 comments
Assignees

Comments

@coolmancgfs
Copy link

coolmancgfs commented May 24, 2023

Provider v1.30.2

The script.events.event.keystrokes.credential vault_id property for dynatrace_browser_monitor is failing validation with any string provided.

│ Error: Script validation failed: {"violations":[{"path":"/textValue","message":"Illegal property "textValue""}]}
│ on ../synthetics/browser-cred-test.tf line 1, in resource "dynatrace_browser_monitor" "provider_test":
│ 1: resource "dynatrace_browser_monitor" "provider_test" {

example

resource "dynatrace_browser_monitor" "provider_test" {
  name                   = "terraform test"
  enabled                = true
  frequency              = 1
  locations              = ["GEOLOCATION-B4B9167CAAA88F6A"]
  script {
    type = "clickpath"
    events {
      event {
        description = "keystrokes on password"
        keystrokes {
          simulate_blur_event = true
          credential {
            field    = "password"
            vault_id = "ID"
          }
          target {
            locators {
              locator {
                type  = "css"
                value = ".input-block-level:eq(1)"
              }
            }
          }
        }
      }
    }
  }
}
@coolmancgfs
Copy link
Author

This appears to work fine in v1.30.1

@Dynatrace-Reinhard-Pilz
Copy link
Member

Hello @coolmancgfs,

You've stumbled over a regression bug we've introduced when we fixed #247 in the last release.
It's not really about the vault_id field - the REST API finds a text_value property that's not supposed to be there and doesn't even get to the point of validating the vault_id.

Your problem will be fixed with the upcoming release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants