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

Optionally deploy activity log diagnostic settings beyond public and government #461

Closed
shawngib opened this issue Oct 14, 2021 · 1 comment · Fixed by #478
Closed

Optionally deploy activity log diagnostic settings beyond public and government #461

shawngib opened this issue Oct 14, 2021 · 1 comment · Fixed by #478
Assignees
Labels
bug Something isn't working

Comments

@shawngib
Copy link
Member

Description

Current settings through error in clouds not supporting activity log diagnostic settings. Issue #453 tried setting diagnostic settings API to commonly supported version except the underlying API version doesn't support activity settings config. Its likely 453 can be reversed for now until clouds support this setting since the newer API supports it in public and gov clouds.

Steps to Reproduce

Steps to reproduce the behavior:

  1. deploy to non-public/government cloud

Expected behavior

Diagnostic settings are created for activity logs to send to log analytics

Actual behavior

Error message suggesting activitylogdiagnosticsettingsconfig is unavailable.

Screenshots

Additional context

Further work should be created to track this missing capability, for now this is a work around to prevent error so the result will be no activity logs going to central logging.

Operating System:
Terraform Version:
Cloud (public, Azure Government, etc.):

@shawngib shawngib added bug Something isn't working needs triage labels Oct 14, 2021
@brooke-hamilton brooke-hamilton changed the title use environment variable to exclude deploying activity log diagnostic settings beyond public and government Optionally deploy activity log diagnostic settings beyond public and government Oct 19, 2021
@glennmusa
Copy link
Contributor

glennmusa commented Oct 21, 2021

I think opt-in central logging is the right call. 👍

But, unless there's some reason to change all diagnostic settings to an older provider, I don't think we need to revert #453 since the newer provider is already used everywhere else in source and known to work in deployments other than when it is necessary to opt-out of central logging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants