We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When following the documentation in trying to report back on the supported features for an azure org, I'm receiving an empty set
I would expect to see this similar output
"Agentless Scanning", "Auto Protect", "Remediation", "Serverless Function Scanning", ])
This is the current output
features_supported_azure_tenant = toset([])
running the following terraform deployment
terraform { required_providers { prismacloud = { source = "PaloAltoNetworks/prismacloud" version = "1.5.0" } } } provider "prismacloud" { json_config_file = "../.prismacloud_auth.json" } data "prismacloud_account_supported_features" "azure_account" { cloud_type = "azure" account_type = "account" deployment_type = "azure" } output "features_supported_azure_account" { value = data.prismacloud_account_supported_features.azure_account.supported_features } data "prismacloud_account_supported_features" "azure_tenant" { cloud_type = "azure" account_type = "tenant" deployment_type = "azure" } output "features_supported_azure_tenant" { value = data.prismacloud_account_supported_features.azure_tenant.supported_features }
The text was updated successfully, but these errors were encountered:
Should be fixed with #270
Sorry, something went wrong.
@sgordon46 The documentation has been updated for better clarity in the onboarding flow, and this improvement is part of the v1.5.1 release.
No branches or pull requests
Describe the bug
When following the documentation in trying to report back on the supported features for an azure org, I'm receiving an empty set
Expected behavior
I would expect to see this similar output
Current behavior
This is the current output
Possible solution
Steps to reproduce
running the following terraform deployment
The text was updated successfully, but these errors were encountered: