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

Add azure speech service keys #35210

Merged
merged 4 commits into from Jun 9, 2020
Merged

Add azure speech service keys #35210

merged 4 commits into from Jun 9, 2020

Conversation

JillianK
Copy link
Contributor

@JillianK JillianK commented Jun 8, 2020

Adding the azure speech service keys for future use in the text to speech block.

Background

We are incrementally trying to merge this PR

Links

Reviewer Checklist:

  • Tests provide adequate coverage
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

@maddiedierker
Copy link
Contributor

looking at the original PR again, it does look like we missed the linked change in config.yml.erb

@maddiedierker
Copy link
Contributor

@uponthesun can we get your review this PR? i think we've added keys in the correct places (minus the one mentioned in my comment above, which we'll add), but i haven't gone through this process before.

Copy link

@uponthesun uponthesun left a comment

Choose a reason for hiding this comment

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

Just want to double check, you've already added the secrets for each environment with these instructions? https://github.com/code-dot-org/code-dot-org/blob/staging/config/secrets.md#creatingupdating-a-secret

@@ -214,6 +214,10 @@ firebase_max_table_rows: 20000
firebase_max_record_size: 4096
firebase_max_property_size: 4096

# Azure keys for speech service

Choose a reason for hiding this comment

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

config.yml.erb acts as the defaults across all environments, so if you want them in every environment, you should only need to add them here, and not in the development/staging/test/production/levelbuilder yml files. (It would still work the way it is right now, it's just redundant.)

@maddiedierker
Copy link
Contributor

Just want to double check, you've already added the secrets for each environment with these instructions? https://github.com/code-dot-org/code-dot-org/blob/staging/config/secrets.md#creatingupdating-a-secret

yep! we added those last week, so they should be available in all environments.

Copy link

@uponthesun uponthesun left a comment

Choose a reason for hiding this comment

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

I'd recommend you remove the redundant config from the environment-specific files. After that, if it passes drone, then ship it!

@JillianK JillianK merged commit 584f7be into staging Jun 9, 2020
@JillianK JillianK deleted the applab-tts-secrets branch June 9, 2020 18:38
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.

None yet

3 participants