Maria Bazhlekova

@chauncey-garrett We're working on it currently! It will be available in v3.0.0 of the Terraform Provider coming this summer.

Hi @trustthewhiterabbit 👋 the Synthetics resources use our legacy REST API which doesn't use GUIDs. We're currently working on migrating the resources to the new GraphQL API which will return...

@ivanaguilario We've had some intermittent issues in the Alerts API. Can you confirm that you're still seeing this problem?

Hi @PhilippTreupel 👋 this work is currently in progress as we migrate Synthetics to the new API. It will be out with v3 of the Provider expected this summer.

@gitcos I understand that it's confusing. The synthetics resource uses our legacy REST API which only requires an API key. Other resources use our GraphQL API which requires an account...

Our GraphQL API also requires an API Key to make requests and many endpoints also require an account ID argument but not all. An example would be the [alert policy...

All of those are true

@knapo Thank you for your PR! One thing, can you reword your commit message to follow conventional commits? Like this `fix: link to newrelic_entity`

Hi @MartinSMadsen 👋 we're currently working on #1453 and when we complete the API migration the new Synthetics Monitor resource will support setting different runtimes. We expect to have the...

Hi @kohbis thank you for your contribution! We follow conventional commits for the New Relic Terraform Provider. Can you re-word your commit messages to the following format? - `docs: Update...