-
Notifications
You must be signed in to change notification settings - Fork 6
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
drop zoom oauth refresh token #819
base: rc-v0.5.0
Are you sure you want to change the base?
Conversation
|
||
lifecycle { | ||
ignore_changes = [ | ||
value, # key difference here; we don't want to overwrite values filled by the external process | ||
insecure_value, |
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.
What happens if for example client_id
is wrongly provided if is not sensitive? Does value
will update insecure_value
on second attempt ?
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.
if this is in lifecycle, then TF shouldn't change resource even if it believes changes are needed in EITHER value
or insecure_value
@@ -81,3 +81,21 @@ sufficient, but as of May 2024 are no longer available for newly created Zoom ap | |||
Once the scopes are added, click on `Done` and then `Continue`. | |||
|
|||
6. Activate the app |
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.
Features
Fixes
String
rather thanSecureString
usedTODO
Change implications