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

drop zoom oauth refresh token #819

Open
wants to merge 8 commits into
base: rc-v0.5.0
Choose a base branch
from

Conversation

eschultink
Copy link
Member

Features

  • zoom account id, client id don't need to be sensitive

Fixes

  • fix AWS parameter store stuff so String rather than SecureString used

TODO

  • test carefully that bug previously noted is no longer a problem; possibly pin AWS provider version to avoid it

Change implications

  • dependencies added/changed? no
  • something important to note in future release notes? yes, ppl will see a change


lifecycle {
ignore_changes = [
value, # key difference here; we don't want to overwrite values filled by the external process
insecure_value,
Copy link
Contributor

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 ?

Copy link
Member Author

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you can include an screenshot like this on this step too:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants