feat: setup Southwark with S3 Power Automate integration tokens plus howto doc #3931
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Removed vultr server and associated DNS entries |
…ss/southwark-s3-power-automate-setup
DafyddLlyr
approved these changes
Nov 12, 2024
Comment on lines
21
to
+23
| FILE_API_KEY_NEXUS=👻 | ||
| FILE_API_KEY_BARNET=👻 | ||
| FILE_API_KEY_SOUTHWARK=👻 |
There was a problem hiding this comment.
Probably about time we moved these to team_integrations as well I think 👍
Comment on lines
+95
to
+96
| req.headers["api-key"] as string, | ||
| process.env.FILE_API_KEY_SOUTHWARK!, |
There was a problem hiding this comment.
Ideally we'd also constrain this to Southwark requests, but the current S3 setup doesn't support this.
jamdelion
approved these changes
Nov 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Southwark is ready to replicate Barnet's work on the S3/Power Automate integrations - this sets up 4x API tokens for them to do so. See how-to doc for further explanation.
All encrypted values have been added to
teams_integrationtable via prod Hasura console & synce to staging already. AWS S3pizza-secretshas also been updated with staging file api key values.