-
Notifications
You must be signed in to change notification settings - Fork 393
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
[datadog_api_key] Fix bug introduced in 3.55.0 for organisation that doesn't have Remove config enabled #2857
Conversation
…doesn't have Remove config enabled
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ecdatadog looks good just a small suggestion, let me know when this is ready for re-review thanks!
docs/resources/api_key.md
Outdated
@@ -28,7 +28,7 @@ resource "datadog_api_key" "foo" { | |||
|
|||
### Optional | |||
|
|||
- `remote_config_read_enabled` (Boolean) Whether the API key is used for remote config. Warning : default value is true for backwards compatibility Defaults to `true`. | |||
- `remote_config_read_enabled` (Boolean) Whether the API key is used for remote config. Should be put to true only if remote config is enabled in /organization-settings/remote-config |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- `remote_config_read_enabled` (Boolean) Whether the API key is used for remote config. Should be put to true only if remote config is enabled in /organization-settings/remote-config | |
- `remote_config_read_enabled` (Boolean) Whether the API key is used for remote config. Set to true if remote config is enabled in `/organization-settings/remote-config`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Took in account but add only
: Set to true only if
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left you a small suggestion Nvm, looks like Alicia got to this one :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
Fixes #2847
Remove config is configured globally at org level (see /organization-settings/remote-config).
remote_config_read_enabled
argument of api_key is always set tofalse
remote_config_read_enabled
argument is set by default totrue
but can be set explicitly tofalse
Proposed fix :
remote_config_read_enabled
, it will be the default value (true if RC is enabled, false if not) . Similar behavior as in <3.55.0remote_config_read_enabled
tofalse
, it will always worksremote_config_read_enabled
totrue
,You will get this error if you set the argument while RC is not enabled at org level :