Skip to content

Provider uses name of TLS configuration rather than ID to find #1173

@themaxsandelin

Description

@themaxsandelin

We noticed this while we were trying to synchronize our state with what we had live in Fastly and ran into issue with the provider not finding the configuration we had in place while we had the right ID referenced. Turns out it searches by the name, which isn't optimal since that could change and be subject to encoding issues. Could it be replaced with using the ID to find the configuration?

return diag.Errorf("your query returned no results. Please change your search criteria and try again.")

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions