You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow Reaper to start up with access to Vault but no S3 credentials
Reaper does not crash on startup if it cannot retrieve S3 credentials from vault
Reaper is still able to retrieve dataset secrets from Vault
Technical Notes:
Reaper will already bypass getting S3 credentials if it does not have a secrets endpoint, but this disables dataset secret retrieval as well
Why?
Starting a new pipeline from scratch does not require Reaper to immediately have all its capabilities. Hosted datasets are rare in the current instance, and might not be needed for new instances. Adding S3 credentials to Vault is a manual process that can be avoided.
The text was updated successfully, but these errors were encountered:
ksmith-accenture
added
dev
On Hold
Assigned to cards who were originally under the column titled 'On Hold'
and removed
On Hold
Assigned to cards who were originally under the column titled 'On Hold'
labels
Jul 9, 2021
What?
Allow Reaper to start up with access to Vault but no S3 credentials
Technical Notes:
Why?
Starting a new pipeline from scratch does not require Reaper to immediately have all its capabilities. Hosted datasets are rare in the current instance, and might not be needed for new instances. Adding S3 credentials to Vault is a manual process that can be avoided.
The text was updated successfully, but these errors were encountered: