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

S3 docs #521

Merged
merged 1 commit into from
Jun 25, 2024
Merged

S3 docs #521

merged 1 commit into from
Jun 25, 2024

Conversation

csansoon
Copy link
Contributor

Describe your changes

DOCS!

Checklist before requesting a review

  • I have updated the documentation if necessary

Copy link

changeset-bot bot commented Jun 19, 2024

⚠️ No Changeset found

Latest commit: 5be4496

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@csansoon csansoon changed the base branch from main to canary June 19, 2024 12:33
"storage": {
"type": "s3",
"bucket": <your-s3-bucket-name>,
"region": <your-s3-bucket-region>,
Copy link
Contributor

Choose a reason for hiding this comment

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

Recommend using LATITUDE__ env variables here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I recommended it using a Note underneath the code.

Copy link
Contributor

Choose a reason for hiding this comment

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

I see but what's the point recommending here the non-secure way

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Testing, for example. That's what I have been using

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, but this is dangerous. You can test by setting the values in .env vars when we have all the pieces. Docs should not encourage storing secrets in git. People can commit it by mistake

s3:
accessKeyId: <your-access-key-id>
secretAccessKey: <your-secret-access-key>
region: <your-region>
Copy link
Contributor

Choose a reason for hiding this comment

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

Same

@csansoon csansoon changed the base branch from canary to temp-parquet-files June 19, 2024 12:37
@csansoon csansoon force-pushed the temp-parquet-files branch from e907c53 to a2a4949 Compare June 21, 2024 07:42
Base automatically changed from temp-parquet-files to canary June 21, 2024 07:46
@andresgutgon andresgutgon merged commit f260532 into canary Jun 25, 2024
4 checks passed
@andresgutgon andresgutgon deleted the s3-docs branch June 25, 2024 15:43
@github-actions github-actions bot locked and limited conversation to collaborators Jun 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants